Use of field type in tables

Hi ppl,
Is there any disadvantage if I create a table with fields for which I don't assign a data element. Instead, I write the Data Type, Length and Short Text manualy ?
Eg, I have a field COST_CTR for which I don't assign the field type as KOSTL. Instead I maintain direct type as CHAR / 10 / Cost Center.
What difference does it make, if any?
Regards.

(On second thought, i am not sure if defining check table will overcome this limitation)
I think not, as the check field in the foreign table has to use same domain as the check table field for which the condition is checked. This means that in order that could be positive we must provide data element for that field. This is the only way to make that field inherit the domain.
Typing the field direclty will not fullfil the above condition then, hence not input help available.
Regards
Marcin

Similar Messages

How we can use XREF1_HD field of BKPF table.

Hi,
How we can use XREF1_HD field of BKPF table.
Ritu Verma

Hello,
Sadashivan is absolutely right.
You can update this field while posting with using standart substitution or using Business transaction event 00001120.
If you use BAPI_ACC_DOCUMENT_POST and want to fill this fields, you can use RWBAPI01 business transaction event also.
Regards,
Burak

Implications of not using mandt field in SAP table.

Hi Everyone,
Can anybody please let me know the diadvantage and the impact of not using the mandt field at the key field in the db table. And what will be the impact if the customer upgrades the system and if the tables doesnt have this field. Any help will of great use to me.
Thanks,
Prashant.

SAP has the concept of client dependent and client-independent data. This is controlled by the mandt field as the first field in a table which makes it a client dependent table. as there can be multiple clients supported in a single sap system, it is better to have this differentiation so that the data in one client can be clearly distinguished from that of another.
however, this does not hold for certain types of data such as the customizing data which is to be maintained singly across all clients. Thus, such tables which need to have a single definition of data across all clients available in the system should be made client independent, that is , without the mandt field in the table.
once you use client-dependent tables, different clients in the system can even be used as different logical systems, and this certainly helps if data is segregated in multiple client scenario..

How to instantiate class using GUID field from a table

Hi,
There is a class ' /MRSS/CL_SGD_COMPLEX_DEMAND ' and method /MRSS/IF_SGE_COMPLEX_DEMAND~ITEMS_GET.
Actual requirement is field called GUID from the table instantiate the class and i can use its methods to get the reference to assign object.

If i understand the requirement correctly , you need to perform items_get based on the guid. Then create the constructor with a parameter for your GUID , then store this guid in a class member variable. And then you can use the same in the ITEMS_GET( ).
Regards
Kavindra

Using other field types SIT in SSHR

Hi, I've created a form based on an SIT.
KEY_FLEX|SEGMENT1|SEGMENT2 e.t.c
But everything shows up as a text field. Is it possible to make some fields show up as a textarea (bigger and wider) and other types. Thank you

Hi,
According to your post, my understanding is that you wanted to manage file types.
You can share documents or folders in OneDrive for Business. When you share documents and folders, you can decide whether to let people edit them, or just view them.
You can also map SharePoint libraries to your local drive, then you can manage (adding/updating/changing/deleting) files from either SharePoint or file drive.
More information:
Share documents or folders in OneDrive for Business
Map SharePoint Libraries with local file drive – A step-by-step guide
Thanks,
Linda Li
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

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

How to update xmltype field in the table

hi
I have table in DB which contains xmltype field. When I am dragging this table by wizard on a panel and run my project I cannot edit any field in this table and save its data it shows an error. But when I am not using xmltype field in a table then my program runs well.
How can I fix this proble?

repost

No records when inputting new field from linked tables.

I have linked two tables in a report. If I use only fields from one table, no problem. As soon as I add a field from the other table no records are pulled. I am using the same filed "IncidentID" in both tables as a link. If I attempt to pull the "IncidentID" from the second table no records are pulled. There does not appear to be any key fields or indexes in either table if that helps.

Here are the SQL queries. The first string is without any fields from "WorkLog". The second is after adding the field "WorkLog.Incident Number" to the form.
SELECT "HPD_Help_Desk"."Incident Number", "HPD_Help_Desk"."Reported Date", "HPD_Help_Desk"."Direct Contact Site", "HPD_Help_Desk"."Assignee", "HPD_Help_Desk"."Status", "HPD_Help_Desk"."Last Modified Date", "HPD_Help_Desk"."Description", "HPD_Help_Desk"."Priority"
FROM "HPD:Help Desk" "HPD_Help_Desk"
WHERE "HPD_Help_Desk"."Status"='Pending' AND ("HPD_Help_Desk"."Assignee"='Debbie Kiolbasa' OR "HPD_Help_Desk"."Assignee"='John L King' OR "HPD_Help_Desk"."Assignee"='Ligaya Plumlee' OR "HPD_Help_Desk"."Assignee"='Ryan Keeler')
ORDER BY "HPD_Help_Desk"."Assignee"
SELECT "HPD_Help_Desk"."Incident Number", "HPD_Help_Desk"."Reported Date", "HPD_Help_Desk"."Direct Contact Site", "HPD_Help_Desk"."Assignee", "HPD_Help_Desk"."Status", "HPD_Help_Desk"."Last Modified Date", "HPD_Help_Desk"."Description", "HPD_Help_Desk"."Priority", "HPD_WorkLog"."Incident Number"
FROM "HPD:Help Desk" "HPD_Help_Desk" INNER JOIN "HPD:WorkLog" "HPD_WorkLog" ON ("HPD_Help_Desk"."Incident Number"="HPD_WorkLog"."Incident Number") AND ("HPD_Help_Desk"."InstanceId"="HPD_WorkLog"."InstanceId")
WHERE "HPD_Help_Desk"."Status"='Pending' AND ("HPD_Help_Desk"."Assignee"='Debbie Kiolbasa' OR "HPD_Help_Desk"."Assignee"='John L King' OR "HPD_Help_Desk"."Assignee"='Ligaya Plumlee' OR "HPD_Help_Desk"."Assignee"='Ryan Keeler')
ORDER BY "HPD_Help_Desk"."Assignee"
BTW - The "Left Outer Join" receives the errors noted in above post whereas the default "Inner Join" just comes back with empty records.
Unable to use the third party tools due to restrictions on loading software. Also we are unable to access the lower level database.
Thanks

FM to get short description of the fields in standard table.

Hello all,
How to get the short description of the corresponding field name in the standard table using the field name and table name??
Thanks for your understanding..
Kindly help me..anyone..please...

Use view DD03VT.
Use a select query to fetch the required description of the field from view DD03VT passing fields TABNAME, FIELDNAME, DDLANGUAGE in WHERE condition
Using this you can get any text ShortFieldLabel, Medium Fld Labl, Long Fld Label of a field

Updation of Custom Fields in AFRU table Using Customerexit

Hi all,
I added two fields in CO11n Tcode using SCREEN EXIT - CONFPP07 and iam trying to update these two fields in AFRU table
using CONFPP05. But iam unable to update these two field .
see this code in CONFPP05
LOOP AT afrud_tab.
    afrud_tab-zzshift = wa_afrud-zzshift1 .
    afrud_tab-zzoperator = wa_afrud-zzoperator1 .
    MODIFY afrud_tab.
ENDLOOP.
Plz help me regarding this..

Thanks for reply
Ya i added two fields in confpp07 .
see the code :
*& Include           ZXCOFTOP
tables : afrud.
DATA : WA_AFRUD TYPE AFRUD,
        IT_AFRUD TYPE TABLE OF AFRUD.
Include           ZXCOFU24
MOVE afrud-zzshift1 TO wa_afrud-zzshift1.
MOVE afrud-zzoperator1 TO wa_afrud-zzoperator1.
Even though it is not updating . except these two fields.
Regards,
Srinivas

Error while adding user fields to user table using vb6.0

Hi,
I am adding a user tables using vb6.0 using DIAPI.
I am able to add the user table successfully.
I am getting the following error when i am adding the fields to the table.
"The metadata object for this object cannot be updated, since it's ref count is bigger than 0."
My code is as follows:
    oUserFieldsMD.TableName = TABLE_NAME_ITEM_LOCN
    oUserFieldsMD.Name = vTableFields(0, lCount)
    oUserFieldsMD.Description = vTableFields(1, lCount)
    oUserFieldsMD.Type = vTableFields(2, lCount)
    oUserFieldsMD.EditSize = CLng(vTableFields(3,lCount))
    lRetCode = oUserFieldsMD.Add
This error does not come up when i try to add the field to my table using the vb sample provided by SAP.
Your help will me much appreciated.
Thanks.

Hi Satish,
The problem is that you added the table and the objetc that you used to add the table is not freed properly. You need to free the object and then the reference count to that table will be 0 - which will enable you to add the fields
e.g
Dim pUTables As SAPbobsCOM.UserTablesMD
'Do your stuff
Set pUTables = Nothing
Dim pUFields As SAPbobsCOM.UserFieldsMD
'Do your stuff
Set pUFields = Nothing

Dynamic table with field type table

Hi,
I´m using "cl_alv_table_create=>create_dynamic_table" to create a dynamic table for ALV Grid.
But...I need to use colors in ALV, then I need to declare a field type LVC_S_SCOL in dynamic table from "cl_alv_table_create=>create_dynamic_table".
How can I declare this in fieldcat?
The code:
Creating dynamic table
DATA: table_agrup TYPE REF TO data,
        line_agrup TYPE REF TO data.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog           = t_fieldcat
    IMPORTING
      ep_table                  = table_agrup
    EXCEPTIONS
      generate_subpool_dir_full = 1
      OTHERS                    = 2.
    ASSIGN table_agrup->* TO .
Printing ALV
CALL METHOD obj_grid->set_table_for_first_display
    EXPORTING
      is_variant                    = w_variant
      i_save                        = 'A'
      is_layout                     = w_layout
    CHANGING
      it_outtab                     =
      it_fieldcatalog               = t_fieldcat
      it_sort                       = t_sort
    EXCEPTIONS
      invalid_parameter_combination = 1
      program_error                 = 2
      too_many_lines                = 3
      OTHERS                        = 4.
Thanks.

It is not possible with the METHOD cl_alv_table_create=>create_dynamic_table to include another table inside that newly generated table.
I have tried to do it with the code and I got the dynamic table created after at the end of the program.
In the code,
<DYN_TABLE> has same effect as your <table> variable
<DYN_WA> has same effect as your <HEADER>
REPORT ZTEST_NP_DYNAMIC.
DATA: DY_TABLE TYPE REF TO DATA,
      DY_LINE TYPE REF TO DATA.
FIELD-SYMBOLS: <DYN_TABLE> TYPE STANDARD TABLE,
               <DYN_WA>,
               <DYN_FIELD>.
FIELD-SYMBOLS: <FS> TYPE ANY.
* To generate the Dyanmic table with the COLOR
DATA: LS_SOURCE TYPE STRING.
DATA: LT_SOURCE LIKE STANDARD TABLE OF LS_SOURCE WITH HEADER LINE.
DATA: L_NAME LIKE SY-REPID.
DATA: L_MESSAGE(240) TYPE C,
      L_LINE TYPE I,
      L_WORD(72) TYPE C.
DATA: L_FORM(30) TYPE C VALUE 'TABLE_CREATE'.
LT_SOURCE = 'REPORT ZTEST_SUBROUTINE_POOL.'.
APPEND LT_SOURCE.
LT_SOURCE = 'FORM TABLE_CREATE USING I_FS TYPE ANY.'.
APPEND LT_SOURCE.
LT_SOURCE = 'DATA: BEGIN OF LT_GENTAB OCCURS 0.'.
APPEND LT_SOURCE.
LT_SOURCE = 'DATA: BUKRS TYPE BUKRS. '.
APPEND LT_SOURCE.
LT_SOURCE = 'DATA: BKTXT TYPE BKTXT. '.
APPEND LT_SOURCE.
* you can add your fields here.....
LT_SOURCE = 'DATA: COLOR TYPE lvc_t_scol. '.
APPEND LT_SOURCE.
LT_SOURCE = 'DATA: END OF LT_GENTAB.'.
APPEND LT_SOURCE.
LT_SOURCE = 'DATA: POINTER TYPE REF TO DATA.'.
APPEND LT_SOURCE.
LT_SOURCE = 'CREATE DATA POINTER LIKE STANDARD TABLE OF LT_GENTAB.'.
APPEND LT_SOURCE.
LT_SOURCE = 'I_FS = POINTER.'.
APPEND LT_SOURCE.
LT_SOURCE = 'ENDFORM. '.
APPEND LT_SOURCE.
L_NAME = 'ZTEST_SUBROUTINE_POOL'.
CATCH SYSTEM-EXCEPTIONS GENERATE_SUBPOOL_DIR_FULL = 9.
GENERATE SUBROUTINE POOL LT_SOURCE NAME L_NAME
           MESSAGE L_MESSAGE LINE L_LINE WORD L_WORD. "#EC CI_GENERATE
ENDCATCH.
IF NOT L_MESSAGE IS INITIAL.
MESSAGE E000(0K) WITH L_MESSAGE L_LINE L_WORD.
ENDIF.
ASSIGN DY_TABLE TO <FS>.
PERFORM (L_FORM) IN PROGRAM (L_NAME) USING <FS>.
ASSIGN DY_TABLE->* TO <DYN_TABLE>.
* Create dynamic work area and assign to FS
CREATE DATA DY_LINE LIKE LINE OF <DYN_TABLE>.
ASSIGN DY_LINE->* TO <DYN_WA>.
Write: 'bye'.
Regards,
Naimesh Patel

V-41 tcode error :Table 304 is not defined for use with condition type PR00

Hi All,
I am trying to create a BDC using the transaction V-41.
The first screen has fields:
ConditionType and Table, where I have to fill values ZPM1 and 800 respectively.
But as soon as I enter the tcode v-41 and say enter, the above mentioned fields are already having the values 'PR00' and ' 304'. Normally if you take an example fo t-code VA02, all fields are blank.
Then an error message is displayed:
Table 304 is not defined for use with condition type PR00
This behaviour is not allowing me to use the BDC feature.
Please advise me on why this is happening. What are the possible solutions I can use to clear these values programmatically?
Can anything be done via customizing?
Regards,
Namita.

Dear ILHAN ,
Well the problem you are facing is having the following solution:
Table 304 is not defined for use with condition type PR00
Message no. VK024
Diagnosis
The selected condition type does not fit in the condition table, that is the basis for the condition record. Alternatively the selected condition type is not included in the condition types that were selected on the selection screen or that are defined in the variant of the standard selection report.
Procedure
Úse F4 help to choose a valid condition type.
If this does not give you the required condition type, check in Customizing for condition types and the related access sequences.
In the condition maintenance also check Customizing for the selection report (pricing report), that you have selected in the navigation tree, using the standard condition table as a reference.
I hope this helps.
It has worked for me.
I gave it a try and what I am getting using the transaction V-41 is create Price condition (PR00) : Fast Entry.
Please award points if you find it useful.
Regards,
Rakesh

Use of field "Shipping type" independent of the route

Hi colleagues,
I have a request according to field "shipping type" VSART in the order header (can be entered in the shipping tab).
The only thread I can find is [this|https://forums.sdn.sap.com/click.jspa?searchID=12663893&messageID=5380384], but its not helpful.
I have route determination enabled, which is working wonderful.
But now I want to use the field "shipping type" independent of the route, for additional information in an Idoc.
If I propose the field with any value the system issues the error "Shipping type xx does not match shipping type xx for route yyyyxx". This is due to the check against the shipping type in the route definition.
Does somebody know if its possible to disable this cross check to be able to place independent information of the route in the shipping type?
Thanks in advance.
Jens

Hi,
I have gone into transaction f.01 and am unable to find the component Transaction type in dynamic selections. If however you want to find Transacttion type 120 use transaction SE16n and table ANEKPV add in the transaction types (technical name BWASL) add other parameters example company code, period etc to get the related information.
Award points if useful.
Sadie Gajanand

Use of field - Transaction Type in F.01

Dear All,
Can anyone explain the use of field Transaction Type in Dynamic Selection in transaction code F.01.
If I have understood correctly, these are related to fixed assets. If I select any transaction type, say for instance 120, which is related to acquisitions, F.01 should display the related figures.
However, I do not get any display, inspite of having various transactions with transaction type 120.
Can anyone explain me why this is happening?

Hi,
I have gone into transaction f.01 and am unable to find the component Transaction type in dynamic selections. If however you want to find Transacttion type 120 use transaction SE16n and table ANEKPV add in the transaction types (technical name BWASL) add other parameters example company code, period etc to get the related information.
Award points if useful.
Sadie Gajanand

Use of field type in tables

Similar Messages

Maybe you are looking for