Adding additional sap object BUT000 in dms object link.

Hi Experts,
My requirement is adding business partner (SAP object BUT000 ) in DMS object link.
BUT000 is not present as standard sap object list in object linking.
I have gone through SAP documentation and understood following things.
1) Program two screens for the following module pools for the SAP object that is to be linked additionally:
     u2013 SAPLCV00
     u2013 SAPLCVIN
question start: Does this means add one screen lets say screen 5000 to function pool  SAPLCV00 and
                        add one screen 5000 to function pool SAPLCVIN with SAP access key.
question end:
The process logic must be according to that of screen 0204 in program SAPLCV00 and must not be changed.
question start: Does this means simply copy PBO and PAI of screen 0204 and put it in screen 5000.
question end:
Create the function module OBJECT_CHECK_XXXX (XXXX = name of the SAP object).
question start: does this means create FM OBJECT_CHECK_BUT000 in my case.
question end:
If this object can be classified, this function module already exists in the standard system. Otherwise, copy the existing function module OBJECT_CHECK_EQUI (linking of equipment) and change it to suit the new object.
question start: does this means if FM OBJECT_CHECK_BUT000 does not exist in SAP system create it by copying
                        FM OBJECT_CHECK_EQUI.
                        Is it ok if I keep the logic of FM OBJECT_CHECK_EQUI as it is.
question end:

Hi Sunil,
For adding new object first maintain this object in key fields in spro.
You need to add the DMS sceen to the perticular object sceen with screen exit.
The object sholud reflect in DMS and DMS screen should reflect in object t-code.
Check in SE80 if there is no screen exit available for the object ,need enhancement.
I hope this will help you much.
Regards,
Ravindra

Similar Messages

  • Add New Object in a DMS Object Link

    Hi everybody,
    i am trying to create an object link to Service Entry Sheet.  (tcode: ML81N, ESSR-LBLNI)
    by sap instructions i did this step:
    "You must create two new screens with the same number for the module pools SAPLCV130 and SAPLCV140 .
    The processing logic must follow that of screen 1204 in program SAPLVC130."
    and this step:
    Create function module OBJECT_CHECK_XXXX (XXXX = ESSR ) which i have copied from OBJECT_CHECK_EQUI .
    I have done above step .
    I created Screen For SAPLCV130 and SAPLCV140 with screen No 1272. give same flow logic of screen 1204.
    I created Function Module OBJECT_CHECK_ESSR.
    After this What I have to do for displaying  ESSR object in DMS as Object Link. 
    Please Guide me as soon as possible.
    Thanks
    Pranesh

    Hi,
    Since I think you already followed the below steps :
    1. In the standard system, there are already two special screens for the module pools SAPLCV130 and SAPLCV140 for the linked SAP object.
    You must create two new screens with the same number for the module pools SAPLCV130 and SAPLCV140. The processing logic must follow that of screen 1204 in program SAPLVC130.
    2. Create function module OBJECT_CHECK_XXXX (XXXX = object name) If the object can be classified, this function module already exists .
    Otherwise copy the function module for linking equipment DOCUMENT_CHECK_EQUI and change it as required for the new object.
    Kindly go through the below once :
    Link :[http://help.sap.com/erp2005_ehp_02/helpdata/en/2c/3fe93bad3ce333e10000000a114084/frameset.htm].
    you define the object link in DMS customizing
    e.g.For EBAN maintain screen number 247 in "Maintain view for screens to DMS object links" Then link EBAN to your document type
    Hope it helps you.
    Thanks
    Arbind
    Edited by: Arbind Prasad on Feb 24, 2011 5:46 PM

  • Add ESSR Object in a DMS Object Link

    Hi everybody,
    i am trying to create an object link to Service Entry Sheet. (tcode: ML81N, ESSR-LBLNI)
    by sap instructions i did this step:
    "You must create two new screens with the same number for the module pools SAPLCV130 and SAPLCV140 .
    The processing logic must follow that of screen 1204 in program SAPLVC130."
    and this step:
    Create function module OBJECT_CHECK_XXXX (XXXX = ESSR ) which i have copied from OBJECT_CHECK_EQUI .
    I have done above step .
    I created Screen For SAPLCV130 and SAPLCV140 with screen No 1272. give same flow logic of screen 1204.
    I created Function Module OBJECT_CHECK_ESSR.
    After this What I have to do for displaying ESSR object in DMS as Object Link.
    Please Guide me as soon as possible.
    Thanks
    Pranesh

    Hey Pranesh
    Go to IMG -> Cross-Application Components -> Document Management ->  Control Data -> Maintain Screen for Object Link
    Add the SAP objec and Screen
    Go to IMG -> Cross-Application Components -> Document Management ->  Control Data -> Define Document Types
    Choose the document type you want to add the object link
    Define object link
    and add object and screen number
    BR/Håkan

  • Additional sap objects links in dms

    hi, all
    i have an issue in dms.
    1] the custemer needs dms link with routing
    2] needs dms link with bom header and bom item
    i think,
    case 1. needs additional object setting, plz explain in details
    case 2 .dms not allows to link bom header and bom item. give sugession
    rds
    ben

    Hi Ben,
    for object link settings please see the following WIKI page for all necessary customizing steps:
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/plm/ca-dms-Object+link
    Generally all standard object screens are included in function group CV130, which could be displayed in transaction SE80.
    For BOM header the object is 'STKO_DOC' and for BOM item it is 'STPO_DOC'. The screen are the following:
    STKO_DOC: 0258
    STPO_DOC: 0257
    Regarding the routing link I think document could only be used in routings but not linked. So the document have to be added directly in the routing itself. Maybe note 372499 could be useful for this issue.
    Best regards,
    Christoph
    P.S.: Please reward points for useful information.

  • Branching to DMS doc from SAP object trans screen(newly createdobject link)

    Hi
    I have created a new document type and been able to attach a new sap object to that DMS document and view it in the object link of that document in CV02n, Cv03N. My problem is how to display the document from sap object screen (vice versa is always possible)
    For standard object already available such linking is provided by SAP
    (like in mm03->Extras->Document data) but I have added a new SAP object say OIGV. How to browse to ducument data from o4v2, o4v3 transaction. Is there any generic strategy for enhancing each and every SAP object transaction screen to branch to its linked DMS document
    With best of regards
    Saurav Choudhury

    Hi Sai,
    regarding your description I would kindly ask you to go to transaction DC10 and mark a document type where the necessary object is linked under 'Define object links'. Choose the right object and display its details by double-click. Then you will see the field 'Create document' where you have to enter a value '1' (using transaction) or '2' (simple creation). Please enter a value and flag the 'Additional function' checkbox too.
    Based on your description I'm sure that you are using the 'simple creation' mode for this kind of object type in the DMS customizing. Please note that for the simple creation of documents mandatory fields (if set in customizing) cannot be filled and this will lead to error messages.
    Please note that the value "1" for the creation of documents is used to enable a user to simple attache a word file on object side without going to the transaction CV01n. Therefore the system behaviour is different then creating a document by CV01n and attaching a word file to it.
    However, you can change the behaviour how the document is created from equipment master transaction if you change the customizing in transaction DC10 like this:
    If you maintain the value "2" for creation of documents, the user is put to transaction CV01n for the creation of document info records. So maybe this would solve the issue.
    Best regards,
    Christoph

  • Adding new object TAB to DMS

    Hi, all
    I want add new new tab as my new object type. which is not available in standard set ie screens  class CV130 TC 'SE80'
    the new object requirment as per customer
    1] Routing
    2] Inspection Lot
    3] Plan Maintanence
    4] Clibration
    Give procedure how to customize these new objects, which r not available as std screens for dms object links.
    rgds
    Ben

    Hi Benaka,
    In standard SAP system you can link DIR to various other SAP Objects for that, in customization setting choose :
    Cross-application component->Document management->Control Data->Maintain Key fields.
    Following steps to be followed as per IMG activity documentation(click & follow the step).
    Regards,
    Seema Pilankar
    If it useful reward me the points.

  • DMS object links to SRM

    Hi,
    You can used this method to create object links between DMS different ECC objects (See below) Is there anybody who can tell me if you can use the same method to create object links between DMS and SRM objects? It should be very helpful for me.
    Thanks in advance
    //Håkan
    Adding Other Objects
    Purpose
    You can also link documents with SAP objects for which no linking is supported in the standard
    SAP System.
    Prerequisites
    In Customizing for the Do
    cument Management ,SAP objects that you want to link to document info records, by choosing Control Data ® Maintain key fields.
    Process
    Program two screens for the following module pools for the SAP object that is to be linked additionally:
    u2013 SAPLCV00
    u2013 SAPLCVIN
    The process logic must be according to that of screen 0204 in program SAPLCV00 and must not be changed.
    Create the function moduleOBJECT_CHECK_XXXX (XXXX = name of the SAP object).
    If this object can be classified, this function module already exists in the standard system. Otherwise, copy the existing function module OBJECT_CHECK_EQUI (linking of equipment) and change it to suit the new object.
    Result
    After you have completed the above, documents can be linked with the SAP object that you have added. You define the settings for this in Customizing for the Document Management System (see:
    Object Links).

    Hey Manghes,
    The business scenarie is that poeple working in only SRM not in ECC system at all and they want easyly reach or link some document in DMS to SRM objects by using object links.
    BR
    //Håkan

  • DMS Object Link for SRM

    Dear All,
    Can you please provide me the object link for SRM( Inbound Delivery).
    Our team requirenment we should need to integrate with SRM through DMS (object link)
    So provide me the solution?
    Thanks
    Edited by: RS on Aug 26, 2010 1:14 PM

    Hi RS,
    Kindly follow following steps. Add the new object in DMS object link and DMS screen on new object screen with help of Abap'r.
    This can be achived with help of Abap'r and following steps:
    Purpose
    You can also link documents with SAP objects for which no linking is supported in the standard SAP System.
    Prerequisites
    In Customizing for the Do cument Management , you must maintain the key fields for the SAP objects that you want to link to document info records, by choosing Control Data  Maintain key fields.
    Process
    1. Program two screens for the following module pools for the SAP object that is to be linked additionally:
    u2013 SAPLCV00
    u2013 SAPLCVIN
    The process logic must be according to that of screen 0204 in program SAPLCV00 and must not be changed.
    2. Create the function module OBJECT_CHECK_XXXX (XXXX = name of the SAP object).
    If this object can be classified, this function module already exists in the standard system. Otherwise, copy the existing function module OBJECT_CHECK_EQUI (linking of equipment) and change it to suit the new object.
    Result
    After you have completed the above, documents can be linked with the SAP object that you have added. You define the settings for this in Customizing for the Document Management System (see: Object Links).
    Regards,
    Ravindra

  • DMS object link to MIGO tcode - attach to GRN

    Hi,
    Our scenario requires us to link documents with specific GRN number via MIGO tcode. This is a non-std object and the logic
    1.Program two screens for the following module pools for the SAP object that is to be linked additionally:
    u2013 SAPLCV00
    u2013 SAPLCVIN.......
    is not helpful at all and incomplete.
    Could anyone please let know what needs to be done from GRN object side to enable documents to be attacvhed.
    Archivelink is not an option because several documents need to follow life ctycle and versioninG.

    Hello,
    It is a two step process:
    1. Screen activation in SAP DMS
    2. Screen activation in SAP Object
    Please follow below steps:
    1. Configuration of screens as per SAP suggestion & Maintenance of Standard Structure MCDOKOB
    Material document number filed MBLNR need to be included in the standard structure.
    2. For t code MIGO, following function module needs to be maintained - OBJECT_CHECK_MSEG
    3. Maintenance Key Fields
    MSEG MIGO MBLNR MBN
    4. Maintain Object link
    MSEG Material Document Screen Number (enter the screen number which you have configured)
    Use the above created object link in your document type.
    5. Implementation of BADI - MB_MIGO_BADI, this is to activate the sceen of documents in MIGO
    I have not done this. So it is possible that i would have missed some step.
    But I am sure, it will help you a lot.
    Thanks & Regards,
    Mihir Popat

  • DMS Object Link at Maintenence Order and Service order level

    Hi SAP Gurus,
    We had a requirement for maintaining DMS Object at Service order and maintenence order level, as Standard DMS does not provide any Standard Object link at Order level, we went for development and following the Standard procedure i could bring the Order Tab in CV01N Object Links, and also i could search the relavent maintenence order and maintain documents relevant to it,
    But the biggest problem now is i could not create DIR from the Maintenence or service order screen IW31, and the document i have placed at the order is not visible in the order screen at all,
    i know it is some sort of enhancement in the Order screen to allow DMS Documents to appear in the Order screen to provide this funtionality.
    let me pls know what exactly has to be done, as there is no config at the order level to get the DMS Screen, as DMS is not a standard object at the order level.
    one approch as suggested is modifiying the Order screen or using Screen Exit Enhancement for Order but not sure which one to use or how to move ahead,
    Thanks n Regards
    Priya S

    Dear Christoph Hopf
    Many Thanks for your answer,
    i went through the said SAP Note, but it only speaks about the notifications level, where SAP itself has provided the standard DMS Object links, and iam in latest ECC-6 version where this note  is taken care of i think,
    iam looking for creating DMS Document (DIR) from the maintenence Order IW31 transaction screen, and have developed new Object link for Maintenence order,
    but the main problem is, iam not able to create DIR from the IW31 Screen directly as Maintennce order is not a standard SAP Object,
    please let me know how to get the list of documents that i have attached to a maintenence order to appear in the IW32 maintenence order screen, and also we need to create the documents (DIR) directly from IW31 / 32 screens.
    Thanks and Regards,
    PriyaS
    Edited by: Priya S on Aug 19, 2009 1:50 AM
    Edited by: Priya S on Aug 20, 2009 1:54 AM
    Edited by: Priya S on Aug 24, 2009 6:24 PM

  • SAP naming conventions: customer DDIC objects, ABAP programming

    SAP Note 16466 Customer name range for SAP objects contains the SAP naming conventions for customer DDIC objects. Rule of thumb is that the names reserved for customer objects start with 'Y' or 'Z'. However, this note contains the naming convention for DDIC objects only.
    ABAP Code Inspector (transaction SCI) contains the following naming convention for ABAP programming:
    - Global types: T_
    - Global constants: C_
    - Global data: gv_
    - Global field-symbols: FS_
    - Global parameters: P_
    - Global select-options: S_
    - Global field-groups: FS_
    - Local types: LT_
    - Local constants: LC_
    - Local data: v_
    - Local field-symbols: LFS_
    This is the only place I know for ABAP programming naming convention. Does SAP has somewhere else any additional naming convention guidelines for ABAP programming?
    Thanks in advance for your help.
    Regards,
    Jarmo Tuominen

    Naming convention guidelines for ABAP programming is available in here: [Manage Successful Customer Development|https://websmp206.sap-ag.de/~sapidb/011000358700004444532001E].
    Naming Data Types and Objects
    The names of data types and objects have the form: <Classifier>_<Data type>_<Descriptor>.
    The names of data types and objects have up to 30 characters.
    Exceptions: names of input parameters and select options have up to 8 characters, and <Data type> and _ are omitted.
    First component: Classifier
    T Data type
    C  Constant
    G  Global data object
    L  Local data object
    FS Field symbol
    P  Input parameter
    S  Select option
    P  Formal parameter in form
    FM Formal parameter in function
    Second component: Data Type
    <t> Elementary data type, optionally followed by length
    C<n> Type C of length <n>
    N<l> Type N of length <n>
    X<l> Type X of length <n>
    D    Type D
    T    Type T
    I    Type I
    P<d> Type P with <d> decimals
    F    Type F
    WA  Work area
    IT  Internal table
    Third component: Descriptor
    Use meaningful English names. Later, your code may be maintained or analyzed by a programmer or support consultant who is not familiar with another language.
    Use only alphanumeric characters (A-Z and 0-9) and separate words with underscores (_). Hyphens are reserved for separating components in structured data types.
    Examples:
    G_I_COUNTER (global counter)
    T_IT_BOOKING_LIST (type for list of bookings)
    G_IT_BOOKINGS (global internal table of bookings)
    PSMOKER (input parameter for smoker flag: note omission of data type and _ for brevity)
    Edited by: Jarmo Tuominen on Feb 21, 2011 2:13 PM

  • Text ID for text object BUT000 does not exist

    Hi Experts.
    I am doing data migration using LSMW with IDoc. I have this error message "Text ID for text object BUT000 does not exist" when processing the IDoc.
    Can anyone tell me what is this error about and how could i fix it. A step by step guide would be nice. Really need advice urgently.
    I'll definitely rewards points.
    Regards,
    Julianna

    for this u need to maintain the text object and its related text id using the TC: SM31 in rel. view of  ur tcode( like MM01, Va01 etc).
    first get the view names(1 for text object and 2 for text id) from fun. people.
    then go to sm31 with 1 view, create BUT000 .
    then go to sm31 with 2 view, maintain text id for the text object:BUT000.

  • SAP Document Attachment - Services for object

    Hello Guys,
    Find the below attachment about a PPT on " services for object"
    <a href="http://verbellacmg.com/asug_2006_walls_404.ppt">Services for object icon - ppt</a>
    Would be highly usefull.
    Regards,
    Murali.S
    Reward if its Usefull.

    Hi, There is no standard report or transaction to get this other than looking at the object through the transaction that creates those attachments, also you can go through SAP OSS note 530792
    Refer below link for creating a report for your requirement
    http://it.toolbox.com/wiki/index.php/GOS_Finding_Attachments_or_Links_to_an_Object_in_SAP/ABAP
    For second requirement it can be handled by Authorization, discuss with your basis guys

  • DMS Object link Material authorization

    Hi Gurus,
    I want to give authorization to users only linking Material, how can i achieve this as i tried with C_DRAD_OBJ - Create/Change/Display/Delete Object Link, but it is giving full access to all other objects, but i want to permit only for MATERIAL.
    I appreciate for your response.
    Regards
    Naveen

    Hi Naveen,
    As Chandu said, you need to be specific while providing the authorisations in the authorisation object C_DRAD_OBJ. This object contains 4 authorisation field values
    1) ACTVT(Activity) which allows creation/change/delete of object link from the DIR
    2) DOKOB(Linked SAP Object) - In combination with activity you can assign specific objects like MARA,PRPS etc. to user
    3) STATUS: In combination of above 2, you can also restrict using specific status i.e. only in 'CR-Created" status user can change/delete the object link.
    4) DOKAR: The user is allowed to create/change...object links in which all document types.
    If you have already specified all these above, then the user is getting other object links authorisations through some other role. Check with SUIM tcode for details.
    Regards,
    Ravi

  • What is SAP name space for different objects.

    Hi Guys,
    Kindly let me know the SAP name spaces for different objects.
    Thanks

    hi,
    Naming Conventions in ABAP Objects 
    Global classes and interfaces that you create in the Class Builder are stored in the class library and administered by the R/3 Repository: they therefore have the same namespace as all other Repository objects (database tables, structures, data elements, and so on).
    It is therefore necessary to have naming conventions for object types and their components and to use them uniformly within program development.
    The following naming convention has been conceived for use within the SAP namespace:
    If you do not observe the naming conventions for object types (classes and interfaces), conflicts will occur when the system creates persistent classes, since it will be unable to generate the necessary co-classes.
    Namespace for Components
    A single namespace within a class is shared by:
    All components of the class itself (attributes, methods, events, constructors, interfaces, internal data types in the class, and aliases)
    All public and protected components of the superclasses of the class.
    Method implementation has a local namespace. The names of the local variables can obscure those of class components.
    Naming Convention
    The naming convention has been kept as general as possible to avoid adversely influencing the naming of objects.
    General Remarks
    When you choose names for development objects, you should:
    Use English names
    Use glossary terms when possible
    For example, CL_COMPANY_CODE instead of BUKRS
    In compound names, use the underscore character (_) as a separator. Since names are not case-sensitive, this is the only character that you can use to separate names.
    Example: CL_COMPANY_CODE, CL_GENERAL_LEDGER_ACCOUNT
    Names should describe the action, not the implementation of the action.
    Example: PRINT_RECTANGLE, not RECTANGLE_TO_SPOOL
    Conventions for Object Types
    Class and interface names in the class library belong to the same namespace as data elements, tables, structures, and types. They are maintained centrally in table TADIR.
    Class in the class library
    CL_<class name>
    The class name should be made up of singular nouns.
    CL_COMPANY_CODE, CL_GENERAL_LEDGER_ACCOUNT
    Interfaces in the class library
    IF_<interface name>
    The same naming convention applies to interfaces as to classes.
    IF_STATUS_MANAGEMANT, IF_CHECKER
    Local classes in programs
    (recommendation)
    LCL_<class name>
    The class name should be made up of singular nouns.
    LCL_TREE_MANAGEMENT
    Local interfaces in programs
    (recommendation)
    LIF_<interface name>
    The sane naming convention applies to interfaces as to classes.
    LIF_PRINTER
    Recommended naming conventions are not compulsory. However, if you use prefixes for these class and interface names, you should use those listed above.
    Conventions for Components
    Method name
    <method name>
    Method names should begin with a verb:
    GET_STATUS, CREATE_ORDER, DETERMINE_PRICE
    Events
    <event name>
    Event names should have the form
    <noun>_<participle>:
    BUTTON_PUSHED, COMPANY_CODE_CHANGED, BUSINESS_PARTNER_PRINTED
    Local type definitions within a class
    (recommendation)
    TY_<type name>
    TY_INTERNAL_TYPE, TY_TREE_LIST
    Data definitions (variables)
    <variable name>
    When you name variables within a class (CLASS-DATA or DATA), avoid using verbs at the beginning of the name (to avoid conflicts with method names).
    LINE_COUNT, MARK_PRINTED, MARK_CHANGED, STATUS
    Data definitions (constants)
    (recommendation)
    CO_<constant name>
    CO_MAX_LINE, CO_DEFAULT_STATUS, CO_DEFAULT_WIDTH, CO_MAX_ROWS
    Recommended naming conventions are not compulsory. However, if you use prefixes for these class and interface names, you should use those listed above..
    Concrete Method Descriptions
    Attribute access
    SET_<attribute name>, GET_<attribute name>
    Methods that access attributes of any kind should be prefaced with GET_ or SET_.
    GET_STATUS, SET_USE_COUNT
    Event handler methods
    ON_<event name>
    Methods that handle events should begin with ON, followed by the name of the event that they handle.
    ON_BUTTON_PUSHED, ON_BUSINESS_PARTNER_PRINTED
    Methods that perform type conversions
    AS_<new type>
    AS_STRING, AS_ISOCODE
    Methods that return a Boolean value
    These methods may not return any exceptions.
    Recommendation: Use SPACE and 'X' to represent false and true respectively.
    IS_<adjective>
    IS_OPEN, IS_EMPTY, IS_ACTIVE
    Check methods
    CHECK_<objective>
    CHECK_AUTHORIZATION, CHECK_PROCESS_DATE
    Local Conventions Within Methods
    For parameters
    The parameters are regarded from the point of view of the method that implements them:
    IMPORTING parameters
    IM_<parameter name>
    EXPORTING parameters
    EX_<parameter name>
    CHANGING parameters
    CH_<parameter name>
    RESULT
    RE_<result>
    Using prefixes is NOT compulsory. However, if you do use them, use those listed above.
    For exceptions
    The following table contains a series of possible exception names, that can also be used generically (for example, NOT_FOUND could also be used as DATE_NOT_FOUND)
    EXCEPTION
    Meaning
    ACTION_NOT_SUPPORTED
    The requested action or function code is not supported.
    CANCELLED
    If a method uses a dialog to find out what has to be dome (for example, a list of choices), and the user chooses "Cancel", you can set this exception.
    EXISTING
    A new object that you want to create already exists in the database.
    FAILED
    The method could not be executed because of the current environment. This exception is intended for cases where the method cannot be executed because of variable system circumstances.
    ..._FAILED
    Part of the method could not be completed because of the current environment. (OPEN_FAILED, CLOSE_FAILED, SELECTION_FAILED, AUTHORIZATION_FAILED)
    FOREIGN_LOCK
    Data is locked by another user.
    INCONSISTENT
    Object data in the database is inconsistent.
    ..._INCONSISTENT
    The component data for … of an object in the database is inconsistent.
    INVALID
    The object data entered is incorrect (for example, company code does not exist). Compare NOT_QUALIFIED.
    ..._INVALID
    The component data entered for an object is incorrect. Compare NOT_QUALIFIED.
    INTERNAL_ERROR
    Last resort. Only use this exception if you cannot be more precise about the nature of the error.
    NOT_AUTHORIZED
    The user does not have the required authorization.
    NOT_CUSTOMIZED
    The object requested is not correctly customized.
    ..._NOT_CUSTOMIZED
    The component … of the requested object is not correctly customized.
    NOT_FOUND
    Unable to find the requested object.
    ..._NOT_FOUND
    Unable to find component … of the requested object.
    NOT_QUALIFIED
    The combination of input parameters is insufficient to run the method. Compare INVALID.
    ..._NOT_QUALIFIED
    One parameter of the method is not qualified.
    NUMBER_ERROR
    Error assigning a number.
    SYSTEM_ERROR
    This exception is set if the Basis system returns an unexpected error message.
    regards,
    sudheer.

Maybe you are looking for