EEWB field length modification error

Hi,
In our system, an EEWB project is already exist for custom fields in Quotation's product item (CI_EEW_CUSTOMER_I).
I want to change the field length of those custom fields. Thus, I run the wizard of this EEWB project and change some of the field length.
After the wizard and some of the tables are converted, following error occurs:
Task CRM_BTX_ADD_NEW_FIELDS CD3100
deleting of existing BAdI Implementation "ZEEW_CUSTOMER_I01" failed
Moreover, the EEWB icon is changed to red & broken.
How can I continue and make it back to normal?

Hi
The error is coming because EEWB does changes in the ABAP dictionary objects. Now you are not able to delete the field properly thats why you are getting the error
Once you delete the field then only you can process.
check your customizing in transaction EEWC.
Look at note 649336 to set up the customizing.
Regards
Manohar

Similar Messages

I am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

i am trying to generate purchase order and i create a BAPI also which is active.
But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Hi,
Yeah i tried my Z_BAPI in R3 and then giving some ERROR.
This is my CODE-
FUNCTION ZBAPIPOTV2.
*"*"Local Interface:
*" IMPORTING
*"     VALUE(POHD) TYPE ZPOHD OPTIONAL
*"     VALUE(POITEM) TYPE ZPOITEM OPTIONAL
*" TABLES
*"      RETURN STRUCTURE BAPIRET1 OPTIONAL
data: ls_pohd type bapimepoheader,
         ls_pohdx TYPE bapimepoheaderx,
         lt_poit TYPE TABLE OF bapimepoitem,
         lt_poitx TYPE TABLE OF bapimepoitemx,
         ls_poit TYPE bapimepoitem,
         ls_poitx TYPE bapimepoitemx.
   MOVE-CORRESPONDING pohd to ls_pohd.
   MOVE-CORRESPONDING poitem to ls_poit.
   ls_pohdx-comp_code = 'x'.
   ls_pohdx-doc_type = 'x'.
   ls_pohdx-vendor = 'x'.
   ls_pohdx-purch_org = 'x'.
   ls_pohdx-pur_group = 'x'.
   ls_poit-po_item = '00010'.
   APPEND ls_poit to lt_poit.
   ls_poitx-po_item = '00010'.
   ls_poitx-po_itemx = 'x'.
   ls_poitx-material = 'x'.
   ls_poitx-plant = 'x'.
   ls_poitx-quantity = 'x'.
   APPEND ls_poitx to lt_poitx.
CALL FUNCTION 'BAPI_PO_CREATE1'
   EXPORTING
     POHEADER                     = ls_pohd
    POHEADERX                    = ls_pohdx
*   POADDRVENDOR                 =
*   TESTRUN                      =
*   MEMORY_UNCOMPLETE            =
*   MEMORY_COMPLETE              =
*   POEXPIMPHEADER               =
*   POEXPIMPHEADERX              =
*   VERSIONS                     =
*   NO_MESSAGING                 =
*   NO_MESSAGE_REQ               =
*   NO_AUTHORITY                 =
*   NO_PRICE_FROM_PO             =
*   PARK_COMPLETE                =
*   PARK_UNCOMPLETE              =
* IMPORTING
*   EXPPURCHASEORDER             =
*   EXPHEADER                    =
*   EXPPOEXPIMPHEADER            =
TABLES
    RETURN                       = return
    POITEM                       = lt_poit
    POITEMX                      = lt_poitx
*   POADDRDELIVERY               =
*   POSCHEDULE                   =
*   POSCHEDULEX                  =
*   POACCOUNT                    =
*   POACCOUNTPROFITSEGMENT       =
*   POACCOUNTX                   =
*   POCONDHEADER                 =
*   POCONDHEADERX                =
*   POCOND                       =
*   POCONDX                      =
*   POLIMITS                     =
*   POCONTRACTLIMITS             =
*   POSERVICES                   =
*   POSRVACCESSVALUES            =
*   POSERVICESTEXT               =
*   EXTENSIONIN                  =
*   EXTENSIONOUT                 =
*   POEXPIMPITEM                 =
*   POEXPIMPITEMX                =
*   POTEXTHEADER                 =
*   POTEXTITEM                   =
*   ALLVERSIONS                  =
*   POPARTNER                    =
*   POCOMPONENTS                 =
*   POCOMPONENTSX                =
*   POSHIPPING                   =
*   POSHIPPINGX                  =
*   POSHIPPINGEXP                =
*   SERIALNUMBER                 =
*   SERIALNUMBERX                =
*   INVPLANHEADER                =
*   INVPLANHEADERX               =
*   INVPLANITEM                  =
*   INVPLANITEMX                 =
ENDFUNCTION.
i am trying to generate purchase order and i create a BAPI also which is active. But when i call the BAPI from SYbase Mobile Object RFC then after calling it gives an Error "Conflict when calling a Function Module (Field Length)".

Type conflict when calling a function module (field length)

Dear All,
            I am getting this following error while executing: Type conflict when calling a function module (field length)
This is piece of coding i have writern in my action button.
method SEARCH_MATERIAL .
data:
        node_mat_input TYPE REF TO if_wd_context_node,
        node_mat_output TYPE REF TO if_wd_context_node,
        material TYPE BAPIMATDET-MATERIAL,
        itab TYPE TABLE OF BAPIMATDOA.
node_mat_input = wd_context->get_child_node( 'NODE_MAT_INPUT' ).
node_mat_output = wd_context->get_child_node( 'NODE_MAT_OUTPUT' ).
node_mat_input->get_attribute( EXPORTING name = 'MATERIAL'
                                 IMPORTING value = material ).
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material                    = material
    PLANT                       = plant
    VALUATIONAREA               =
    VALUATIONTYPE               =
    MATERIAL_EVG                =
   IMPORTING
     MATERIAL_GENERAL_DATA       = itab
    RETURN                      =
    MATERIALPLANTDATA           =
    MATERIALVALUATIONDATA       =
node_mat_output->bind_table( itab ).
endmethod.
Attributes are:
Node name = INPUT its structure is BAPIMATDET
INPUT attributes = MATERIAL of type BAPIMATDET-MATERIAL
Thanks,
Gopi.

Hi Amit,
           I have used service call to fetch records from that bapi..
The following is the code generated by service call:-
METHOD execute_bapi_material_get_deta .
declarations for context navigation
DATA:
    node_bapi_material_get_de   TYPE REF TO if_wd_context_node,
     node_exporting   TYPE REF TO if_wd_context_node,
     node_material_general_dat   TYPE REF TO if_wd_context_node,
     node_importing   TYPE REF TO if_wd_context_node,
      lri_element    TYPE REF TO if_wd_context_element.
declarations for fuba parameters
data:
    stru_c_material_general_dat    TYPE if_componentcontroller=>element_material_general_dat.
DATA:
    attr_material    TYPE bapimatdet-material,
    attr_plant    TYPE bapimatall-plant.
get all involved child nodes
node_bapi_material_get_de = wd_context->get_child_node( `BAPI_MATERIAL_GET_DE` ).
node_exporting = node_bapi_material_get_de->get_child_node( `EXPORTING` ).
node_material_general_dat = node_exporting->get_child_node( `MATERIAL_GENERAL_DAT` ).
node_importing = node_bapi_material_get_de->get_child_node( `IMPORTING` ).
get input from context
node_importing->get_attribute(    EXPORTING      name = `MATERIAL`
                                                     IMPORTING      value = attr_material ).
node_importing->get_attribute( EXPORTING       name = `PLANT`
                                                          IMPORTING       value = attr_plant ).
the invocation - errors are always fatal !!!
CALL FUNCTION 'BAPI_MATERIAL_GET_DETAIL'
    EXPORTING
      material =                        attr_material
      plant =                           attr_plant
"      valuationarea =                   wd_This->Valuationarea
"      valuationtype =                   wd_This->Valuationtype
"      material_Evg =                    wd_This->Material_Evg
    IMPORTING
      material_general_data =           stru_c_material_general_dat
"      return =                          wd_This->Return
"      materialplantdata =               wd_This->Materialplantdata
"      materialvaluationdata =           wd_This->Materialvaluationdat
node_material_general_dat->bind_structure( stru_c_material_general_dat[] ).
ENDMETHOD.
                             but the problem is I am getting the following error while compiling...
" stru_c_materialplantdata " is not an internal table - the " OCCOURS n" specification is missing.
Thanks,
Gopi.
Edited by: Yegalaivan on Nov 18, 2009 8:30 AM

Table field length problem

Hi Team,
We r tring to create table with field length 250 and 'CHAR' type and one more field 'STRING 'for unlimited length.While creating table entries ,it is tsking only 130 length for all fields.it is not taking 250 characters for 250 length field.and it is not taking unlimited length for String field.Plz let me know.

Hello Mohan,
CHAR 250 is right. i am not facing any problem.
can you please explain in detail what you have done and what error you are getting.
Regards,
Sujeet
Edited by: Sujeet Mishra on Dec 2, 2009 4:42 AM

Getting correct field length when creating formats for delimited flat files

Using Data Services 3.2 to pull in tsv and Excel source files.
When creating a new format for each file, DS tries to intelligently set the field size for each column. However, it seems to sample only a portion of the file. The end result is that it often determines too short a length for a field.
Is there a way to force it to scan an entire file before it sets the field length? Or alternatively, how to get it to at least throw an error instead of silently truncating my data?

I am not aware of any way to force DS to scan the whole file, or to log a warning when it truncates. The field sizes DS sets by using a sample of the data is only really to give you a starting point, you need to try and determine the maximum possible lengths preferably from someone who understands the source of the data or through profiling. But the profiling method will obviously only be based on the data you have at the time of profiling, new data added to the source later could exceed the field lengths. The way I prefer to handle this is to set all the field lengths to longer than expected, eg. varchar(999) and then use a validation transform immediately after reading the file to check for any fields that exceed the maximum allowed for the target system and send these to an error file/table.

Control an Integer field Length without using Validation ??

Hi,
I have Couple of fields where I need to configure them as Integers.
Now each one has a fixed length that i need to limit to.
But when i create a field of type: integer, i cannot select teh length!!!
To achive this the idea i have is to write a validation which checks length..
But can i achive it without going for a validation on each field???
PS: I am aware that TEXT field can limit the length But it also allows me to enter text values, my requirement clearly says that to allow users to only enter Numeric values..
Did anyone face a similar Case?
Kind Regards
Eva

Hi Eva,
I didn't try in the system, but I feel there are two solutions to achieve your requirement (*of course in both cases you will need to write a simple validation)
Solution 1 : When field is defined as "Integer" in Console.
lets take an example, you want to restrict an integer field with a limit of max 4 characters.
Maximum value of a 4 character integer can be "9999". So, you can put a simple validation to compare the field value with 9999. if the value is less then this means fields values is less than 4 characters, else more than 5 characters.
In this case Your validation expression in expression editor will be:
FIELD NAME<= "9999"
Solution 2 : When field is defined as "Text" in Console.
In this case you can restrict the maximum field length through Console. But you will also need to write a validation to ensure that user is not entering any alphabets or special characters in this field.
In this Case you can use below validation:
HAS_ALL_CHARS(FIELD NAME, "0","9")
This will ensure that field has all characters between 0 and 9 and doesn't hold any special character or alphabets.
In Both cases you will need to set "Automatic Execution" property as "Error". Also please do not manually type any function or value in expression editor. use drop down for fields, operators, functions etc. and enter numeric values using the first blank box before dimension list.
Kindly revert if you face any issues.
-Shiv

FIXED FIELD LENGTH is not constant

Hello Guru's,
This is the question asked in IBM .
What will you do if field length of a field in flat file is not constant or not equal to the FIXED FILED LENGTH ?.
i.e. f1 is of length is 10 and in one row its length is only 9 what will happen and what will you do to overcome this situation.( consider its a FILE TO FILE SCENARIO )
can anyone help me in this regard.
Thanks in advance.

> This is the question asked in IBM .
> What will you do if field length of a field in flat file is not constant or not equal to the FIXED FILED LENGTH ?.
> i.e. f1 is of length is 10 and in one row its length is only 9 what will happen and what will you do to overcome this situation.( consider its a FILE TO FILE SCENARIO )
The ans for this question is very simple.
Since your FIXED FIELD LENGTH is 10 correct. now if any value comes of length 9 or less, then there will be no problem at all. It will work perfectly without doing anything. BUT if your length goes beyond 10 then it will throw an error message which you can see in RWB.
Shorter length is never a problem in case of FIXED FIELD LENGTH.
I hope now you got the ans, but good way to learn is, to create a simple scenario and test it. )
Regards,
Sarvesh

How can I restrict field lengths in a field?

I have a field that I want the user to only enter a 5 character response, not a 4 or 6 character response. Is '?????' field validation the only option?

There is a LEN function that you can use to validate the entry. It returns the length of the field. You could build a validation rule to ensure the field length is 5 and that anything other than 5 characters returns an error message. You would need to build more specific validation rules if your result needed to be numeric or non-numeric. The LEN function only rerturns the length.
Good Luck,
Thom

Leading Zero w/ variable field length...

I'm creating a form in which I need a particular field to:
- Accept/Display a leading zero (or multiple leading zeros);
- Accept numbers numbers;
- Have a maximum field length of six numerals, but with the ability to accept fewer;
- Display an error message if the above criteria are not met.
I have some code (see below), but don't know how to make the field length variable.
var fmt = /^\d\d\d\d\d\d$/;
if(event.value != "")
if(!fmt.test(event.value))
app.alert("Incorrect format, field must contain numbers only.");
event.rc = false;
Make sense...? Can anyone help...?
Thank you.

This drops the leading zero(s) and does not display the error message.
Adjustments...?
Thank you for your promp reply.

UDF for Splitting the nodes based on the field length

HI All,
Target records Record1 to Record4 must be created based on the length of the source field length i.e, if the source field length is only 90 then only 3 records must be created.maximum length of the source field is 120.The source and the target structure are as shown
Source                                  Target
Record                                Record(30)
      Field(120)    ------------->          Field1(10)
                                                 Field2(10)
                                                 Field3(10)
After mapping:-
        Source         ----------->        Target
Record                                Record1(0 to30)
      Field(120)    ------------->          Field1(0 to 10)
                                                 Field2(10 to 20)
                                                 Field3(20 to 30)
                                           Record2(30 to 60)
                        ------------->          Field1(30 to 40)
                                                 Field2(40 to 50)
                                                 Field3(50 to 60)
                                           Record3(60 to 90)
                        ------------->          Field1(60 to 70)
                                                 Field2(70 to 80)
                                                 Field3( 80 to 90)
                                           Record3(90 to 120)
                        ------------->          Field1(90 to 100)
                                                 Field2(100 to 110)
                                                 Field3(110 to 120)
Can any one provide me the code to get this done.
Thanks ,
Vikram

You need no UDF. You can use the substring function, but you should check the length of the string to prevent mapping errors due to the substring function.

Field Length Cannot Be Reduced UDF

I have a problem where i accidentally updated the Alphanumeric UDF to 100 and now i want to reduce its size and it prompts me with an error saying "Field Length Cannot Be Reduced". Any way to fix this?

Hi David,
You will not be able to Reduce Length of UDF once Created.
This is Standard System Behavior.
If its your requirement then Delete existing UDF and then Create again same UDF name with less Length.
Hope this help
Regards::::
Atul Chakraborty

Invalid field format (screen error)

We are using custom module pool report for displaying information. Information display in Table control which has also Radio button option for the further processing. After unicode conversion we are getting error while accessing the screen as "Invalid field format (screen error)" when user select Radio button. In production environment we are not facing any issue, but in Dev + Qas we have this issue. Nothing is changed as all environment are sync. To solve the issue we re-defined the Radion screen element, but no success we are still getting same error. I am not sure whether it is related to Page Format or something else. Could you please let me know whether anybody faced this issue ? For the information, I already searched on SDN and SNote, but there is no post or SNote

Have you checked if there are overlapping fields on the screen.
I've seen simular errors and usually it was beacuse of some change by SAP that made it so that the defined length of the screen field was suddenly to small.
I'm not saying that this is the case in your situation, but it never hurts to try and change the length of your screen field and see if that resolves the issue.
Arthur

Incoming Email Subject Field length increase

Hi,
In CRM 7.0,I need to increase the incoming email Subject Field length ,When i try to modify UI configuration,Subject fields are not enabled for configuration (Other fields in the same screen are enabled for modifications)..
Please give your inputs whether incoming email Subject Field length can be increased? if so,this should be done at UI level or mail form?
Regards
Shan

Hi Prasenjit,
Thanks for your interaction and response.
Actually I can to find out views and class details in CRM 7.0 by using F2 key..
The UI component is CRMCMP_CCS_EML and view is CRMCMP_CCS_EML/MailBody. The implementation class is ZL_CRMCMP_C_MAILBODY_IMPL. Since all the page attributes are string, There is a context class ZCL_CRMCMP_C_MAILBODY_CTXT, But no context node (Like you mentioned type CN as in *CN00, *CN01) within page attribute.
The main issue am facing here is that couldnu2019t figure out where to start the debugging for inbound mails where the subject field is truncated. I usually process inbound mails from SOIN transaction.
Moreover subject field can have more than 40 characters in outgoing mail, but the inbound mail subject field limited to 40 character and rest of them truncated.
Hope you understand my area of concern and provide me your input.
Regards,
Shan

Field Length too big to display

Hi
We have a scenario where the wrong unit of measure was used and resulted in numbers that were too big to display on deliveries and reports eg 555, 000, 000, 000, 000.00. We are now changing the UOM for the affected PNs but wondered if anybody has any other solutions on how SAP can cope with displaying fields that are too large for its defined length for all the old deliveries created previously. Currently these hit run time display errors. We have already extended the field length once but need a more robust solution in case there are any more materials like this.
Thanks

Extending the field length would not make the error going away. Instead it makes it easier for the user to enter wrong units and conversions. As SAP will less often dump, you will encounter your errors much later than now.
analyse your materials and correct the wrong entries, conversions to alternative units are stored in table MARM

GL Account Field length

Hi,
My client wants to change the account field length in the doc entry. Standard account field is length is 16 or 17 digits. Its length has to be reduced to 10 digits.
How can i do this ? Can I do this in the configuration (or) customisation ? If it is customisation what are the tables I need to touch ?
Awaiting for the reply
Thanks,
Krishna

Use Transaction code OB13 to maintain maiximum length of GL account length as 10 apart from this you can also write validation so that if any gl account with more that 10 digits is entered system gives error.
Regads,
Manish Jain
Assign points if it serves your purpose.

EEWB field length modification error

Similar Messages

Maybe you are looking for