Defaulting a date field in the table

Hi Experts,
I need to default a date field(DATBI) in a table to 12/31/9999. Since the date is system specific i cannot hardcode it as 12/31/9999 in the events.
For eg . in our quality system date is maintained as 12.31.9999.
Please let me know how i can implement this.
Regards,
Anjali

In my table say ZXXXX i have a field DATBI. My requirement is to default this field's value to 12/31/9999 while maintaining the table.
Since date field is system specific. For eg , in our Dev system Date format is 12/31/9999. where as in quality it is 12.31.9999, I cannot hardcode it as 12/31/9999.
I need to default the value for field DATBI irrespective of the system.

Similar Messages

Problem with displaying Date field in the table.

Hi All,
I am trying to display data into a table UI Element.
In that data, i have one DATE type field. While displaying data in DATE field, it will display like this "01.02.2009".
Now my requirement is if i want to modify that DATE field, it will allow to modify "01.02.2009" to "26.02.2009".
But while modifying DATE field , I want to show the Calender of that month, in that i have to select the another date.
(Like normal Date UI Element will show that calender).
Can anyone please help me.
Thanks in Advance!
Regards,
Sreelakshmi.

Hi,
Go to the context attribute that was mapped to the DATE field of the table and change the perperty INPUT HELP MODE to AUTOMATIC and it works.
Regards,
Manne.

Changing the attibutes of a field in the table will affect existing data

Hi Experts,
If I want to changne the field attribute of particular field in the table, this table whoes field is changed is used in 15 more tables.Will that affect the data in production after changing the field attributes in all the 15 tables.
Thanks in Advance.
Regards,
IFF

Hi,
Definitely data will effect in all tables and also you have to modify all the programs which are used modified tables.
Regards,
Peranandam

How to select data from a table using a date field in the where condition?

How to select data from a table using a date field in the where condition?
For eg:
data itab like equk occurs 0 with header line.
select * from equk into table itab where werks = 'C001'
and bdatu = '31129999'.
thanks.

Hi Ramesh,
Specify the date format as YYYYMMDD in where condition.
Dates are internally stored in SAP as YYYYMMDD only.
Change your date format in WHERE condition as follows.
data itab like equk occurs 0 with header line.
select * from equk into table itab where werks = 'C001'
and bdatu = <b>'99991231'.</b>
I doubt check your data base table EQUK on this date for the existince of data.
Otherwise, just change the conidition on BDATU like below to see all entries prior to this date.
data itab like equk occurs 0 with header line.
select * from equk into table itab where werks = 'C001'
and <b> bdatu <= '99991231'.</b>
Thanks,
Vinay
Thanks,
Vinay

Changing the Default meta data field property required into not required.

Hi,
Is it possible to change the default meta data field property values in UCM server.
For example consider the meta data Revision field which property required is true, then how to change this property required into not required.
Is this possible or not?
Thanks
Hari

Hari,
in your case (if you don't want to use versioning) I'd rather recommend to change it to hidden than not required. You should be able to do it with standard profiles (the field name, I believe, is dRevision)
I don't think you can have the field empty (in case someone deletes the content).

Need help in Populating a Z-field in the table "MARD"

Hi Group,
I have a requirement like as under:
1)
Need to add a field in the transaction MM01/02/03 screen in the view u2018Plant data / stor. 1u2019. And this field should go into the table u2018MARDu2019 table, by appending the structure and adding this field details in it.
2)
Once I post a value into this field thru the transactions (MM01/MM02/MM03) , I need the value in the screen to be populated into the table u2018MARDu2019 in the Appended Structure field.
Could you please help me out by getting a proper User Exit or BADI which fulfills the requirement?
in Summary, please let me know a User Exit or BADI which will update the Z-field of the table 'MARD'.
Thanks for the help in advance.
Regards,
Vishnu.

please check , it might help you.
How to add fields to MM01 Transaction
How to add a new field in MM01 with CONCEPT as a field?
How to add a new field in MM01, with say contaminent as a field?
HI ALL, How can i add new field in mm01 basicdata1 screen
Add button in MM01 Transaction
i want to add the one field in mm01 application how can i add the field?
If you dont get the answer still , please search the forum you will get many links for your requirement
Regards
Satish Boguda

Date fields in the Maintainence View.

Hello friends,
I created a maintanence view which of 2 steps. This view contains a DATE field of data element type 'DATS". Now the problem is -"
1. In the first screen of the viewI am not able to see only the DATE field(Over view scr).
2. But I able to see the same field in the 2nd screen(Maintanence Screen).
Not only to my View I maintained ' Table Maintanence Generator" to some more tables.There also I am not able to see the date field in the first screen, unless it is a key field.
Thanks in advance.

Hi
Step 1: Create & Maintain Table (SE11)
Screen 101: ABAP Dictionary: Initial Screen
Screen 102: Maintain Table -> Delivery and Maintenance
Screen 103: Maintain Table -> Fields
[] SE11: Enter Table Name -> Create
Enter Table Description (Mandatory Field)
Select Delivery Class
Set maintenance level
Enter Fields, Assign Data Elements
Save Entries
Check Inconsistencies
Activate Table
Go To Technical Settings (SCREEN 104)
Delivery Class: The delivery class controls the transport of table data when
installing or upgrading, in a client copy and when transporting between customer
systems. The delivery class is also used in the extended table
maintenance.
There are the following delivery classes:
A: Application table (master and transaction data).
C: Customer table, data is maintained by the customer only.
L: Table for storing temporary data.
G: Customer table. The customer namespace must be defined in table TRESC. (Use
Report RDDKOR54 here).
E: System table with its own namespaces for customer entries.
S: System table, data changes have the same status as program changes.
W: System table (e.g. table of the development environment) whose
data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL,
etc.).
Data Browser/Table View Maint.: This indicator specifies
whether it is possible to display/maintain a table or view using the maintenance
tools Data Browser (transaction SE16) and table view maintenance (transactions
SM30 and SM31).
MANDT field is mandatory for Client dependant tables
Technical Settings: The technical settings control, for example, table buffering.
Indexes: To speed up data selection, you can create secondary indexes for the table
Append Structure: Append structures are used for enhancements that are not included in the standard.
Screen 104: Maintain Technical Settings
Select Data Class (Mandatory) [APPL0]
Select Size Category (Table size - No. of records - Mandatory) [1 to 6]
Specify Buffering [allowed / not allowed]
Save
Check Inconsistencies
Activate & Go Back to Maintain Table Screen
Data Class: The data class defines the physical area of the database (for ORACLE
the TABLESPACE) in which your table is logically stored. If you choose a data
class correctly, your table will automatically be assigned to the correct area
when it is created on the database.
The most important data classes
are (other than the system data):
APPL0 Master data
APPL1 Transaction data
APPL2 Organizational and customizing data
Size category: The size category determines the probable space requirement for a table in the database.
Buffering: The buffering status specifies whether or not a table may be buffered.
Screen 105: Maintain Table
Screen 106: Maintain Enhancement Category (ECC 6.0 onwards)
-> Extras -> Enhancement Category
Select Enhancement Category
Enhancement Category: Structures and tables that were defined by SAP in the ABAP
Dictionary can be enhanced subsequently by customers using Customizing includes
or append structures. The enhancements do not only refer to structures/ tables
themselves, but also to dependent structures that adopt the enhancement as an
include or referenced structure. Append structures that only take effect at the
end of the original structure can also cause shifts - in the case of dependent
structures - even within these structures.
Screen 107: Maintain Table -> Table Maintenance Generator
Screen 108: Generate Table Maintenance Dialog: Generation Environment
-> Utilities -> Table Maintenance Generator OR [] SE54
Specify Authorization Group [&NC&]
Select Maintenance type [One Step/Two Step]
Mention Screen Numbers [1/2]
Save & Go Back
Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

Sending reports to various recipients using a data field on the report

Hi,
I am currently running Crystal Reports Server 2008 with SP 3 applied.
I was wondering if this was possible.
I have a report that I would like to be sent to an email address field on the table that the report runs from. Fields are something like this:
Amount Due, Invoice #, Client's email address, Date
What I would like CRS to do is send out emails depending on what's on the table. Obviously I would need the server to send out the report to a particular client with only the records that should be for them.
I, for some reason, thought there was an ability to add a field from the report on the email itself using brackets or some sort of variable but I'm not sure if this is true.
If anyone can help, I would appreciate it greatly.
Thanks!

You can use Publications for that. As far as I know this should be supported natively in CRS 2008 with SP3.
Take a look at the demo on building a data-driver publication here:
http://www.sap.com/solutions/sap-crystal-solutions/information-infrastructure/sapcrystalserver/featuresfunctions/index.epx
You have to have CALs (concurrent access licenses) though.
Regards,
Stratos

Problem while saving date field in custom table

Hi,
Iam facing the following problem while saving a date field in custome table
i have a date field zdate in which the value is 02082010.
now when i try to insert this value in the custom table it is getting updated as 20/10/0208 , but it should be 08/02/2010
How can i correct it..
Regards
Kumar

just before saving u might have to use a string reverse FM and then save it..
CALL FUNCTION 'STRING_REVERSE'
EXPORTING
    STRING          = p_string
    LANG            = sy-langu
IMPORTING
   RSTRING          = r_string
EXCEPTIONS
   TOO_SMALL        = 1
   OTHERS           = 2

Number of fields in the table

Hi experts,
How do you obtain the number of fields of a particular table ?
I want the count of the fields of a table.
Thanks in advance,
Chithra.

Check the code below:
DATA: d_ref TYPE REF TO data,
i_alv_cat TYPE TABLE OF lvc_s_fcat,
ls_alv_cat LIKE LINE OF i_alv_cat,
fname TYPE fieldname,
ncomp(9) TYPE n,
rcount(9) TYPE n,
fcount(3) TYPE n.
TYPES: BEGIN OF itab1,
message(50) TYPE c,
END OF itab1.
DATA: g_itab1 TYPE STANDARD TABLE OF itab1.
DATA: wa_itab1 TYPE itab1.
ncomp = 1.
rcount = 0.
TYPES: tabname LIKE dcobjdef-name,
fieldname LIKE dcobjdef-name.
PARAMETER: p_tablen TYPE tabname. "Input table field
DATA: BEGIN OF itab OCCURS 0.
INCLUDE STRUCTURE dntab.
DATA: END OF itab.
FIELD-SYMBOLS : <f_fs> TYPE table,
<f_fs2> TYPE ANY,
<f_fs3> TYPE ANY,
<f_fs4> TYPE ANY.
REFRESH itab.
CALL FUNCTION 'NAMETAB_GET' "Fetches the fields
EXPORTING
langu = sy-langu
tabname = p_tablen
TABLES
nametab = itab
EXCEPTIONS
no_texts_found = 1.
LOOP AT itab .
ls_alv_cat-fieldname = itab-fieldname.
ls_alv_cat-ref_table = p_tablen.
ls_alv_cat-ref_field = itab-fieldname.
ls_alv_cat-seltext = itab-fieldtext.
ls_alv_cat-reptext = itab-fieldtext.
APPEND ls_alv_cat TO i_alv_cat.
fcount = fcount + 1.
ENDLOOP.
WRITE:/ fcount.
WRITE: ' number of column'.
internal table build
CALL METHOD cl_alv_table_create=>create_dynamic_table
EXPORTING
it_fieldcatalog = i_alv_cat
IMPORTING
ep_table = d_ref.
ASSIGN d_ref->* TO <f_fs>. " Dynamic table creation with fields of the
*table
DATA: l_field TYPE fieldname,
l_field1 TYPE fieldname.
SELECT * FROM (p_tablen) INTO CORRESPONDING FIELDS OF TABLE <f_fs>.
"Fetching of the data from the table
rcount = 0.
LOOP AT <f_fs> ASSIGNING <f_fs2>.
rcount = rcount + 1.
DO fcount TIMES.
"Here u can check the validations and process
ASSIGN COMPONENT ncomp OF STRUCTURE <f_fs2> TO <f_fs4>.
IF NOT <f_fs4> IS INITIAL.
MOVE <f_fs4> TO l_field1.
ncomp = ncomp + 1.
ELSE.
CONCATENATE 'IN ROW' rcount 'COLUMN' ncomp 'IS BLANK' INTO wa_itab1.
APPEND wa_itab1 TO g_itab1.
ncomp = ncomp + 1.
ENDIF.
ENDDO.
CLEAR:ncomp.
ENDLOOP.
LOOP AT g_itab1 INTO wa_itab1.
WRITE:/ wa_itab1 'is blank'.
ENDLOOP.
regards
Kannaiah

How to generate test data for all the tables in oracle

I am planning to use plsql to generate the test data in all the tables in schema, schema name is given as input parameters, min records in master table, min records in child table. data should be consistent in the columns which are used for constraints i.e. using same column value..
planning to implement something like
execute sp_schema_data_gen (schemaname, minrecinmstrtbl, minrecsforchildtable);
schemaname = owner,
minrecinmstrtbl= minimum records to insert into each parent table,
minrecsforchildtable = minimum records to enter into each child table of a each master table;
all_tables where owner= schemaname;
all_tab_columns and all_constrains - where owner =schemaname;
using dbms_random pkg.
is anyone have better idea to do this.. is this functionality already there in oracle db?

Ah, damorgan, data, test data, metadata and table-driven processes. Love the stuff!
There are two approaches you can take with this. I'll mention both and then ask which
one you think you would find most useful for your requirements.
One approach I would call the generic bottom-up approach which is the one I think you
are referring to.
This system is a generic test data generator. It isn't designed to generate data for any
particular existing table or application but is the general case solution.
Building on damorgan's advice define the basic hierarchy: table collection, tables, data; so start at the data level.
1. Identify/document the data types that you need to support. Start small (NUMBER, VARCHAR2, DATE) and add as you go along
2. For each data type identify the functionality and attributes that you need. For instance for VARCHAR2
a. min length - the minimum length to generate
b. max length - the maximum length
c. prefix - a prefix for the generated data; e.g. for an address field you might want a 'add1' prefix
d. suffix - a suffix for the generated data; see prefix
e. whether to generate NULLs
3. For NUMBER you will probably want at least precision and scale but might want minimum and maximum values or even min/max precision,
min/max scale.
4. store the attribute combinations in Oracle tables
5. build functionality for each data type that can create the range and type of data that you need. These functions should take parameters that can be used to control the attributes and the amount of data generated.
6. At the table level you will need business rules that control how the different columns of the table relate to each other. For example, for ADDRESS information your business rule might be that ADDRESS1, CITY, STATE, ZIP are required and ADDRESS2 is optional.
7. Add table-level processes, driven by the saved metadata, that can generate data at the record level by leveraging the data type functionality you have built previously.
8. Then add the metadata, business rules and functionality to control the TABLE-TO-TABLE relationships; that is, the data model. You need the same DETPNO values in the SCOTT.EMP table that exist in the SCOTT.DEPT table.
The second approach I have used more often. I would it call the top-down approach and I use
it when test data is needed for an existing system. The main use case here is to avoid
having to copy production data to QA, TEST or DEV environments.
QA people want to test with data that they are familiar with: names, companies, code values.
I've found they aren't often fond of random character strings for names of things.
The second approach I use for mature systems where there is already plenty of data to choose from.
It involves selecting subsets of data from each of the existing tables and saving that data in a
set of test tables. This data can then be used for regression testing and for automated unit testing of
existing functionality and functionality that is being developed.
QA can use data they are already familiar with and can test the application (GUI?) interface on that
data to see if they get the expected changes.
For each table to be tested (e.g. DEPT) I create two test system tables. A BEFORE table and an EXPECTED table.
1. DEPT_TEST_BEFORE
     This table has all EMP table columns and a TEST_CASE column.
     It holds EMP-image rows for each test case that show the row as it should look BEFORE the
     test for that test case is performed.
     CREATE TABLE DEPT_TEST_BEFORE
     TESTCASE NUMBER,
     DEPTNO NUMBER(2),
     DNAME VARCHAR2(14 BYTE),
     LOC VARCHAR2(13 BYTE)
2. DEPT_TEST_EXPECTED
     This table also has all EMP table columns and a TEST_CASE column.
     It holds EMP-image rows for each test case that show the row as it should look AFTER the
     test for that test case is performed.
Each of these tables are a mirror image of the actual application table with one new column
added that contains a value representing the TESTCASE_NUMBER.
To create test case #3 identify or create the DEPT records you want to use for test case #3.
Insert these records into DEPT_TEST_BEFORE:
     INSERT INTO DEPT_TEST_BEFORE
     SELECT 3, D.* FROM DEPT D where DEPNO = 20
Insert records for test case #3 into DEPT_TEST_EXPECTED that show the rows as they should
look after test #3 is run. For example, if test #3 creates one new record add all the
records fro the BEFORE data set and add a new one for the new record.
When you want to run TESTCASE_ONE the process is basically (ignore for this illustration that
there is a foreign key betwee DEPT and EMP):
1. delete the records from SCOTT.DEPT that correspond to test case #3 DEPT records.
          DELETE FROM DEPT
          WHERE DEPTNO IN (SELECT DEPTNO FROM DEPT_TEST_BEFORE WHERE TESTCASE = 3);
2. insert the test data set records for SCOTT.DEPT for test case #3.
          INSERT INTO DEPT
          SELECT DEPTNO, DNAME, LOC FROM DEPT_TEST_BEFORE WHERE TESTCASE = 3;
3 perform the test.
4. compare the actual results with the expected results.
     This is done by a function that compares the records in DEPT with the records
     in DEPT_TEST_EXPECTED for test #3.
     I usually store these results in yet another table or just report them out.
5. Report out the differences.
This second approach uses data the users (QA) are already familiar with, is scaleable and
is easy to add new data that meets business requirements.
It is also easy to automatically generate the necessary tables and test setup/breakdown
using a table-driven metadata approach. Adding a new test table is as easy as calling
a stored procedure; the procedure can generate the DDL or create the actual tables needed
for the BEFORE and AFTER snapshots.
The main disadvantage is that existing data will almost never cover the corner cases.
But you can add data for these. By corner cases I mean data that defines the limits
for a data type: a VARCHAR2(30) name field should have at least one test record that
has a name that is 30 characters long.
Which of these approaches makes the most sense for you?

Search Help on Table Control - Fill more than one field in the table?

Hey everyone,
I have built a screen with a Table Control on it... the fields of the table control are linked to an internal table... The internal table has the line type of a structure I've defined in the data dictionary. Within that structure in the data dictionary, I've linked some fields to search helps (For example, a MATNR and CUSTOMER search help)... I've defined in the structure definition which fields from the search help are to be returned to which fields in the structure.
The problem is, even though I have the search help set to export both the customer number and location when using the search help on the customer field, it still does not fill the location field within the table. Is this a limitation of using search helps within table controls?
I'm also finding that by defining the search help through the structure, instead of directly within the screen, the search help round button does not show up on the field, yet I can still press F4 to bring up the search help. Is there a reason why it's not showing the search help clickable button even though it works fine using F4?
For doing search helps in Table Controls, is it better to just build the search help, attach it directly to the field in the table, and then after the user picks the single field, use the PAI to run a select and fill the rest of the fields required?
Thanks,
Dallas

Hi Dallas,
(1)
What i understood is that you added a search help by defining it in the internal table type for a field customer number..in the search help you have 2 fields customer number and location...user press the search help ..then you need to fill 2 different fields or 1 field?
if you need to fill the customer location or location (only one) then you need to set the "import" in the search help for whichever is required.....
if you need to fill 2 or more different fields..then you can use the technique you have mentioned last , to do a select in PAI and fill the fields....but this you can use if the combination for the fields is unique...eg: u have customer number and location..if customer X can be mapped to location X and location Y..when a select statement is done there are 2 options..so in such cases it is better to leave the option to the user otherwise if there is a clear mapping like customer X can be mapped only to location X then you can use the select..
(2)
usually when you define it as a type in the internal table the icon doesn't show up..but you can do alternative like mentioned..go to the table,find the search help for the required field if present or create a new one if required and place the search help mentioned in the screen itself..so as to see the icon...sometimes users are adamant that they need the search help icon to be seen..so it depends on if your user
(3)
as in the example of customer number and location mentioned we can provide them different search helps and do the needful processing in PAI to fill the fields
Table controls may be used for different purposes and requirements....even a checkbox,push button can be placed as a field in table control and used,but yes most of the time requirements are like what is mentioned in your case...
Regards
Byju

To Display a date field in TSTCT table

Dear Experts,
Recently we got a request to have a date field in TSTCT table. So, that when ever the new transaction is created the date will automatically display in TSTCT table. Now there is only three fields in the table. There is no further settings to regarding the display of date field. Is there any possible cases/BADI's which helps to display the Date field in TSTCT Table. Please help me with possible solutions.
Thanks in advance, Regards,
Harsha.

Dear Eswara,
It is not possible adding field through BADI or exit. But you go into /nSE11 for this table and go to Technical Settings, if the check box 'Log Data Changes' is set then you may be able to display a log of changes made to entries in this table using /nSCU3.
Regards,
Abbas.

Focus lost in Date Field when the property autosubmit="true" is added

Hi,
I am using jdeveloper version 11.1.2.0.0.
The issue I am facing is when I add the property autosubmit="true" for a date field and if I am selecting a date value using date picker, the focus is lost for the date field. But when I remove the property autosubmit="true" for the date field and if I am selecting a date value using date picker, the focus stays in the date field. This I tried in sample application with the default converter and validator. Anybody can help me with this issue?

Hi,
there is a preSubmit event for form objects you can use.
Select your date field, open the script editor and add this script (language is FormCalc) into the preSubmit event.
$ = num2date(date(), "MM/DD/YYYY")

Add a custom-field in the table MARC and manage it in MM01/MM02/MM03

Good day to all of you!
I have this task: To add a custom-field to the table MARC. This custom-field will be managed through the MM01/MM02/MM03 transaction as follows:
In the Basic Data 1 or Basic Data 2 the custom-field data will be added. Let's say the field is MATNR OBSOLETE.
I have searched and implemented the things in customizing: Made a copy of function group MGD1, added the field on the screen.
MY PROBLEM! How to manage it??? When the user enters MM01/MM02/MM03 and update this field, the field should be updated in MARC.
1. I am not sure that this custom-field should be on Basic Data1 or Basic Data2.They want it at plant level.
2. How to manage the data transfer from SAP Standard Program and my Custom Function Group.
PLs: Do not paste me link to sap technical site with that example, because there takes the custom fields and UPDATE a CUSTOM TABLE. I need to update MARC!
All the documentations i have read until now tell you how to add the field, ONLY the first part of the SOLUTION.
Any help, pls?
Good day and thank you!

Hi Alex,
In which way you are trying to update that custom filed. Have you written any logic in EXITS/BADIS?
http://pavelgk.pbworks.com/f/6729224-Implement-Screen-Exit-for-MM01-Adding-New-Fields-in-Screen.pdf
and
Just read the OSS note mentioned earlier.
Symptom
You want to integrate customer-specific fields in material master maintenance.
Other terms
SAPLMGMM, RMDATIND, ALE, CI_MMH1, EXIT_SAPLMGMU_001
Solution
To add customer-specific fields to an existing material master table (such as MARA or MARC) , you can proceed as follows as of Release 3.0C:
      1. Use an append structure to add the fields to the required table in the Dictionary (this is not a modification; for details, see the SAP document "ABAP/4 Dictionary"). In Release 3.x, the length of the field names must be the same as the standard five character fields. This is necessary because of dynamic assignments. As of Release 4.0A, the lengths of the field names can be longer than five characters. If the changes of the fields should be recorded in the change document and taken into account during ALE distribution, set the 'Change document-relevant' indicator for the corresponding data elements. For table MARA in Release 3.x, you must also enhance the database view MARU because the database changes are carried out using this view. This small modification is no longer necessary as of Release 4.0A because the database view MARU is enhanced automatically when you enhance table MARA or the include EMARA (which is the data part of table MARA).
      2. Enhancing online maintenance in customized material master maintenance:
      Define a subscreen with your customer-specific fields in a customer-specific function group created as a copy of the standard function group MGD1.
      In Customizing, assign this subscreen to a maintenance screen using the "Copy customized material master" function. For details, see the Implementation Guide (IMG). As of Release 4.0A, program COPYMGD1 is available. You can use this program to create customer-specific function groups as required. This program is also incorporated in the Customizing function 'Configure customized material master'. Ensure that each field of the subscreen has a field statement in the flow logic, otherwise the data is not transported correctly. You can use subscreen SAPLMGD1 2002 as an example.
      If you want these fields to be subject to standard field selection, you must add new entries for them to the central field table for material master maintenance (T130F):
      Application examples for standard field selection:
      The field is mandatory and is to be flagged with a "?".
      The field belongs exclusively to the purchasing user department. Purchasing data and MRP data are both contained on one screen. However, the MRP controller is not to see the purchasing data.
      The following data is required for each field:
            a) Field name        (T130F-FNAME)
            b) Field selection group (T130F-FGRUP)
            Here, you should use a standard field group if the customer field is subject to the same field selection as the standard fields of the standard field group. If it is not, use a customer-specific field group.
            You must then check and, if necessary, modify the attribute of the field group using the function "Maintain field selection for data screens" in Customizing under "Logistics Basic Data -> Material Master".
            Field groups 111 through 120 that are not used in the standard system are reserved as customer-specific field groups. As of Release 3.0F, additional customer field groups are available. (For details, see the IMG).
            c) Maintenance status (T130F-PSTAT)
            List of the user departments that may maintain the field. You can display possible values by using the input help for the maintenance status field in the Customizing activity "Configure Material Master" when maintaining logical screens.
            d) Reference        (T130F-KZREF)
            This indicator must be set if the field from the reference material should be proposed during creation with reference.
Note: You cannot yet use Customizing to enhance table T130F; you can use only transaction SE16 (Data Browser) or transaction SM31. Future releases will include a separate Customizing function for maintaining customer-specific fields. See Note 306966. By implementing this note you can add entries to table T130F within Customizing. This type of maintenance is possible as of Release 4.5B.
You may change the entries for standard fields only with regard to the reference data and field selection group. Changing other data for standard fields constitutes a modification. Therefore, you cannot use the Customizing function "Assign Fields to Field Groups" to change this data.
In addition, you must not add new standard fields to table T130F.
      3. If you want to maintain customer-specific fields using data transfer by direct input or via ALE distribution, proceed as follows:
      Add the fields to central field table T130F (see above).
      Add the customer-specific fields to the data structures for the data transfer (for example, BMMH1 for the main data).
      Also, add the customer-specific fields to the tables in which the incorrect data is stored during direct input. These tables have the same name as the corresponding master data table and also have the suffix _TMP.
      For example: If you add customer-specific fields to table MARA, you should add the same fields to table MARA_TMP.
      If you use ALE, you must also add fields to the IDoc. To process enhanced IDocs, you can use enhancement MGV00001 with customer exit EXIT_SAPLMV01_002 for creating the IDocs and customer exit EXIT_SAPLMV02_002 for posting the IDocs.
      Prior to Release 3.0E, enhancing structure BMMH1 constitutes a modification. In this case, you must add the new fields tot the end of the structure before the last field (SENDE = record end indicator).
      As of Release 3.0F, structure BMMH1 contains the customer include CI_MMH1, which is part of the enhancement MGA0001. Here, you must proceed as follows:
            a) Add the customer-specific fields to include CI_MMH1.
            The names of the fields in CI_MMH1 must be identical to those of the corresponding fields in material master tables MARA, MARC and so on.
            Important: The fields must be CHAR type fields. Therefore, create CHAR type data elements whose lengths are identical to the output length of your fields in table MARA and so on. Use these data elements in include CI_MMH1, but use the field names from table MARA and so on.
            b) Activate include CI_MMH1.
            c) If you have not used customer structure ZMMH1 before, create it as a copy of structure BMMH1 and delete the standard fields that you do not require. You are not permitted to delete field STYPE and include CI_MMH1 when doing this. If you have already used structure ZMMH1, add include CI_MMH1 to it.
            d) Activate structure ZMMH1. This also adds the customer-specific fields to ZMMH1.
Run program RMDATING. This program generates routines which are supplied to your customer-specific fields from the input file. As of Release 4.5A, you also need to activate the routines/function modules generated by program RMDATING (especially, the MAT_MOVE_BMMH1_XXXX modules). Details about this subject (especially the procedure when using customer structure ZMMH1) are described in the IMG for transferring the material data under item 'Maintain Transfer Structure'. Also, check the declaration of structure WA in program RMMMBIMC to see whether it is declared with sufficient length. If necessary, enhance the declaration (for the time being, this still constitutes a minor modification).
In addition, lengthen domain DI_DATA with CHAR 5000. As of Release 3.1H, this has already been done.
Important: When using customer-specific fields, you can use only structure ZMMH1 to transfer the data. Otherwise, after the next SAP upgrade which contains new standard fields in structure BMMH1, the input files no longer match. If you want these new standard fields to be transferred, add them after your customer-specific fields (the order of the fields in structure ZMMH1 does not need to be the same as the order of the fields in BMMH1).
If you want foreign key dependencies or fixed domain values to be checked, or another check for a customer field, this is possible up to and including Release 3.0D only by modifying the corresponding check function modules. As of Release 3.0E, you can use function exit EXIT_SAPLMGMU_001 (SAP enhancement MGA00001) for these purposes.
If you want to use engineering change management to schedule future changes for your customer-specific fields or you want to use the 'Display at Key Date' function, execute program GENERATE in addition. This program generates the necessary assignments for interpreting the change documents. With regard to engineering change management, you must read Notes 60281, 60973, and 48962.
To date, it is not possible to integrate customer-specific tables in material master maintenance without making a modification. However, you can create customer-specific development objects containing the essential additional logic. You can then integrate these development objects in your system as part of only a minor modification.
check this link. It may helps you to solve your issue.
Thanks
Sravan

Defaulting a date field in the table

Similar Messages

Maybe you are looking for