Making field mara-maktl not mandatory in mm02/mm01

hello sdn people,
hopefully the economy is not in peril where you are...
as my subject line states, i have checked the transactions OMSR / OMS9 and it shows that the field should be display, but it is still required. i would like to turn this off so that this field is not required.
any thoughts? any ideas?
thanks in advance.

Hi Erik,
In the Standard System it will not be possible to save the material if the material group is not ready for input or if it has no value (if it is initial).
You must correct your field selection Customizing for the material group (MARA-MATKL) in Customizing Transaction OMSR accordingly, so that you can maintain the material group in the material master.
Basically, If the purchasing view is filled (ie. the material is eligible for purchasing), the material group (MARA-MATKL) become mandatory.
Thus, the customizing has no effect in this case. If you only fill the Basic view and NOT the Purchasing view, the customizing will have thedesired effect in your System.
The reason for this is that the purchasing programs require this field and MUST be filled in the material master (It is 'hardcoded' this way).
The only way to avoid the error would be to do a modification into the source code !!!
Greetings from Italy,
Mauro

Similar Messages

Making Field-GR BAsed IV Mandatory in ME32L

Hi,
How to make Field-GR Based IV Mandatory in ME32L?
Please suggest.
Thank you.

Hi,
Go to SPRO > Materials Management > Purchasing > Scheduling Agreements > Define Screen Layout at Document Level.
Choose your transaction. (me32) If you need this for me32l and if this transaction is not shown, copy me32 and rename it has me32l. This will create a new entry.
Go into the particular transaction and go to "GR/IR Control". Here change the tick to "Required Entry" in the feild "GR based IV".
This should make the field mandatory.
Regards,
Tharaka

Purchase org. field entry should not be Mandatory for PR creation/release

Dear Experts,
When we are creating PR (ME51N), Purchase organization field entry is mandatory for few user id & in few user id this field is not mandatory. While we are creating PR by which user id, where purchase org. field entry is not mandatory (not fill purchase org. field) & release PR (ME54N) than system ask purchase org no.
Purchase organization field entry should not be mandatory for us when we are creating & release the PR for all user ID's. How can be maintain this things on all user ID's.
Please help us regarding this issue.
Thanks & Regards,
Shatrughan

Hi dear,
Do the following settings in SPRO,
SPRO->MATERIALS MANAGEMENT->PURCHASING->PURCHASE REQUISITION->DEFINE DOCUMENT TYPES.
Here check the Field selection Key for your document type.
Now go to
SPRO->MATERIALS MANAGEMENT->PURCHASING->PURCHASE REQUISITION->DEFINE SCREEN LAYOUT AT DOCUMENT LEVEL
Now double click on the field selection key which you have found earlier and now double click on Reference data,item and set the indocator as optional for Purchasing Organisation key.

User Exit for making the field Bill of Lading Mandatory in Delivery

Please suggest an User Exit for making the field Bill of Lading Mandatory in the Delivery document when we create an inbound delivery.

Hi,
I'm not sure, pls check these
USEREXIT_SAVE_DOCUMENT_PREPARE
EXIT_SAPLV46H_001
NOTIF_EVENT_SAVE
thanks
Mohanprabu C

How to set fields contained in an input structure as not mandatory in WSDL

Hi all,
I hope someone can help me sort out a problem I've been having recently.
I'm generating a WSDL from a function module, which has a structure as the only input parameter. This structure contains a number of fields, which need to be presented as not mandatory in the WSDL descriptor.
I modified the function module by setting the structure and all its contained fields as not mandatory, but when I generate the related WSDL it shows the structure as optional and its subfields as mandatory.
Below is a snippet of the WSDL:
<xsd:element name="Zk4RfcTibcoFatt">
   <xsd:complexType>
      <xsd:sequence>
         <xsd:element name="XZk4Headprev" type="tns:Zk4Headprev" minOccurs="0" />       <-- optional structure
      </xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="Zk4Headprev">
   <xsd:sequence>
      <xsd:element name="RecordType" type="n0:char4" />                                                    <-- non optional parameters
      <xsd:element name="IdricTecn" type="n0:char15" />
      <xsd:element name="IdricFour" type="n0:char15" />
      <xsd:element name="CodOperaz" type="n0:char4" />
   </xsd:sequence>
</xsd:complexType>
I can't understand why the stucture's elements are not defined as optional in the WSDL, while they're configured as optional in the function module definition. I'd expect a minOccurs="0" added to each structure's element definition.
I even tried modifying manually the WSDL from SE80, but it seems it can't be altered in any way.
Has anyone a solution to this problem?
Thanks in advance.
Best Regards.

I tried to do that, but I can't manage to edit the WSDL in SE80, is there a way to do it?
I also tried modifying the WSDL in an external editor, but I can't find a way to switch the edited one with the original one in SAP.
Can you please help me on that?
Thanks in advance for any help you can give me.

Making field mandatory dynamically

HI,
Can anybody send sample code for following logic?
i am having three fields as select options.
consider
BSART
BUKRS
EBELN
In selection screen if BUKRS is initial, I want to change EBELN as mandatory.
else if BUKRS is not initial, EBELN is not mandatory.
usefulll answers will be rewarded.
Thanks & Regards,
Naveen

Hi,
try this
if bukrs is intial.
if EBELN is initial.
message e000 with ' enter ebeln value'
endif.
endif.
regards,
venkatesh

Making old material number mandatory for mm02

hi,
how to make old material number(mara-bismt) mandatory for mm02 transaction.
regards

Hi,
You can do the validation using enhancement "MGA00001", component "EXIT_SAPLMGMU_001".
Regards
Vinod

Add MARA field to CFM1 - Note 360723 not working

Hello all,
We need to add a selection field to CFM1 (program RIMODGEN) : field packaging MARA-MPROF.
We found OSS note 360723 which seems to meet our requirement.
We did the modifications in specified programs, but there is no result : field 'Packaging' is not displayed as a selection field in CFM1.
Yet, we add MARA-PROF as a SELECT OPTION in include RIMODSEL
SELECT-OPTIONS:
         ma_matnr FOR mara-matnr
           MATCHCODE OBJECT mat1
           MODIF ID ma2
           NO-DISPLAY,
         ma_mprof FOR mara-mprof MODIF ID ma2 NO-DISPLAY,
For what reason this code doesn't make the field display is CFM1 screen ?
Note 360723 is quite old (2002). Do you know if there a similar note for more recent versions ?
Thanks a lot,
Rémy

Hi Remy,
Check this notes:
506832
- Transferring MARA segments to APO as of PI.2001.2
902968
- No user exit/BADI to influence selection in CFM1
Kind Regards,
Mariano

Making Fields mandatory in SM30

Does anybody know how can we make fields in SM30 as mandatory. If we have 4 fields in some Z-table, i want to make 2 of the fields mandatory...Pls help me out.

Two methods for this
1. Put code in table maintenance
You have to put some code in while generating table maintenance screen from table maintenace generator which will validate the field when user try to enter data using SM30..
Goto table maintenace generator follow menu path
Enviroment->Modification->Event
Add a event there (01 Before saving the data in the database) and code to validate data... this code will be called before saving data in database via transaction SM30.
2 .Modify screen
Follow menu path Enviroment->Modification->Maintenance Screen
And make the field require field

Make field in Material master mandatory based on the material group

Hello all,
I need to make the field "post to inspection flag" mandatory based on the material group while creating the Material master.
I found options for making the field mandatory based on Material type,Industry sector and plant NOT based on the material group.
Could anyone please provide suggestions on setting up the field as mandatory based on material group while creating material master
Thanks,
Sre

Hi Sre,
You can make Material Group field as Mandatory while Creating Material Master.
SPRO>Log General>Material Master>Field Selection>Maintain Field Selection for Data Screens
Select Screen # 48
In the Field selection (Field Ref.) of (MARA - MAKTL) screen , Change the settings from Optional to Required Entry for T Codes MM01, MM02 or you can select the Material Type ;
Please note this by choosing this selection the fields of Profit Center and Division will also become Mandatory.
Hope this helps,
Best regards
Amit Bakshi

Change pointer in IDOC message-type ARTMAS, for field MARA-LVORM

Hi,
When changing the description of a material in MM02 I am able to sent an idoc using BD21. As this relevant for a change pointer. But when field MARA-LVORM (deletion flag at client level) is chosen, I can not sent an idoc with bd21. How can I make this happen?
thanks.

Hi,
Sorry I interpreted your question in wrong way. Solution I gave was for following requirement.
Every time a material is created or changed a change pointer is created, which serves as a signal for generating IDocs to dependent systems. However, change of material type creates a change pointer that doesn't trigger an IDoc.The purpose is to create the change pointers and send the idocs. Eg. Material type field. As per your reply above I guess change pointer created for LVORM is enough to send the idocs.
KR Jaideep,

Making Customer PO Line Filed Mandatory basing on Customer PO Number in SO

Hi Gurus,
I have the following requirement of making Customer Po Line Filed Mandatory basing on Customer PO Number at Sales Order Line level.
We need to use Sales Order line "Customer PO" line level number to manage the "Cust PO Line" field.
1.When ever "Customer PO" line level modified make Cust PO Line" field empty and as required field.
2.When ever "Customer PO" at line level removed make Cust PO Line" field empty and as non required field.
3.When ever "Customer PO" value at header level is also there,then Customer PO Line value should be Mandatory and Empty after REQUERYING.
Please suggest me the possibilities as soon as possible.Please provide the soltuion steps as soon as possible clearly.
which is the best one to accomplish the given requirement?
1.CUSTOM.pll
2.Form Personalization
3.Form Customization
Note:
RDBMS : 11.2.0.1.0
Oracle Applications : 12.1.3
Oracle Forms Version : 10.1.2.3.0
Thanks,
RS

Hi,
Thanks for your Reply.I have gone through that metalink note 1309458.1.Can you please elaborate the step by step process so that i can complete my task.
Thanks,
RS.

Field symbol has not yet been assigned. ???

Dear Experts ,
W hen i tried to execute my program this error appears :
Short text
    Field symbol has not yet been assigned.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSLVC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 32821).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
and Here is my CODE :
*& Report ZPO
Report ZPO1.
type-pools slis.
PARAMETERS : PO_Doc like EKBE-EBELN DEFAULT '4800000007'.
PARAMETERS : Plant TYPE WERKS DEFAULT '1000'.
PARAMETERS : PO_ORG TYPE EKORG DEFAULT ''.
data TtlS type mara-wesch .
data TtlH type mara-wesch .
data Ttl type mara-wesch .
data ZEKBE type TABLE OF EKBE.
data ZEKBER type EKBE.
data ZEKPO type TABLE OF EKPO.
data ZEKPOR type EKPO.
data ZEKKOR TYPE EKKO.
data ZNAME1F type LFA1-LIFNR.
data ZWGBEZF TYPE T023T-WGBEZ.
data i type n.
data counter type n.
types : begin of SBAGDS,
Serial Type n, "Purchase Order
EBELN like EKKO-EBELN, "Purchase Order
MATNR like EKPO-MATNR, "Material
TXZ01 like EKPO-TXZ01, "Short Text
MATKL like EKPO-MATKL, "Material Group
WGBEZ like T023T-WGBEZ, "Material Group Desc"
SUBMI like EKKO-SUBMI, "GPM
CHARG like EKBE-CHARG, "Batch
LIFNR like EKKO-LIFNR, "Vendor
NAME1 like LFA1-NAME1, "Vendor Name
RECV like mara-wesch, "Received Quantity
REVR like mara-wesch, "Reversed Quantity
DELV like mara-wesch, "Delivered Quantity
end of SBAGDS .
DATA : BAGDS TYPE SBAGDS OCCURS 0 WITH HEADER LINE.
data Struc like BAGDS.
data: gr_table like BAGDS OCCURS 0 WITH HEADER LINE.
data: gt_fieldcat type slis_t_fieldcat_alv, gt_outtab type SBAGDS occurs 0 with header line.
INITIALIZATION.
i = 0.
counter = 0 .
perform field_cat_init using gt_fieldcat[].
FORM field_cat_init using rt_fieldcat type slis_t_fieldcat_alv.
data: ls_fieldcat type slis_fieldcat_alv,
         pos type i value 1.
clear LS_FIELDCAT.
*Column 1
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'Serial'.
ls_fieldcat-SELTEXT_L      = 'Serial'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 2
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'EBELN'.
ls_fieldcat-SELTEXT_L      = 'Purchase Order'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 3
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'MATNR'.
ls_fieldcat-SELTEXT_L      = 'Material'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 4
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'TXZ01'.
ls_fieldcat-SELTEXT_L      = 'Short Text'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 5
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'MATKL'.
ls_fieldcat-SELTEXT_L      = 'Material Group'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 6
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'WGBEZ'.
ls_fieldcat-SELTEXT_L      = 'Material Group Desc'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 7
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'SUBMI'.
ls_fieldcat-SELTEXT_L      = 'GPM'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 8
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'CHARG'.
ls_fieldcat-SELTEXT_L      = 'Batch'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 9
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'LIFNR'.
ls_fieldcat-SELTEXT_L      = 'Vendor'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 10
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'NAME1'.
ls_fieldcat-SELTEXT_L      = 'Vendor Name'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 11
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'RECV'.
ls_fieldcat-SELTEXT_L      = 'Received Quantity'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 12
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'REVR'.
ls_fieldcat-SELTEXT_L      = 'Reversed Quantity'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 13
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'DELV'.
ls_fieldcat-SELTEXT_L      = 'Delivered Quantity'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
endform.
START-OF-SELECTION.
       select SINGLE * from EKKO into ZEKKOR where EBELN = PO_DOC.
       select SINGLE * from EKPO into ZEKPOR where EBELN = PO_DOC.
       select SINGLE NAME1 from LFA1 into ZNAME1F where LIFNR = ZEKKOR-LIFNR.
*         ' Buliding Structure
          Struc-EBELN = ZEKPOR-EBELN.
          Struc-SUBMI = ZEKKOR-SUBMI.
          Struc-LIFNR = ZEKKOR-LIFNR.
          Struc-Name1 = ZNAME1F.
       select * from EKPO into TABLE ZEKPO where EBELN = PO_Doc and WERKS = plant.
       LOOP at ZEKPO into ZEKPOR.
           select SINGLE WGBEZ from T023T into ZWGBEZF WHERE MATKL = ZEKPOR-MATKL .
           counter = counter + 1.
*         ' Buliding Structure
          Struc-Serial = counter.
          Struc-MATNR = ZEKPOR-MATNR.
          Struc-TXZ01 = ZEKPOR-TXZ01.
          Struc-MATKL = ZEKPOR-MATKL.
          Struc-WGBEZ = ZWGBEZF.
*          Calcualting Debit transactions from PO History
           select * from EKBE into table ZEKBE where EBELN = PO_Doc and MATNR = ZEKPOR-MATNR and EBELP = ZEKPOR-EBELP and BWART NOT LIKE '' and SHKZG = 'S'.
           LOOP AT ZEKBE INTO ZEKBER.
               TtlS = TtlS + ZEKBER-MENGE.
           ENDLOOP.
*          ' Buliding Structure
           Struc-CHARG = ZEKBER-CHARG.
           Struc-RECV = TtlS.
           Ttl = TtlS.
           clear TtlS.
*         Calcualting Credit transactions from PO History
         select * from EKBE into table ZEKBE where EBELN = PO_Doc and MATNR = ZEKPOR-MATNR and EBELP = ZEKPOR-EBELP and BWART NOT LIKE '' and SHKZG = 'H'.
           LOOP AT ZEKBE INTO ZEKBER.
               TtlH = TtlH + ZEKBER-MENGE.
           ENDLOOP.
*          ' Buliding Structure
           Struc-REVR = TtlH.
*          Calculating Total Delivered
           Ttl = Ttl - TtlH.
           clear TtlH.
*          ' Buliding Structure
           Struc-DELV = Ttl.
           clear Ttl.
*      Writtng ITAB
       APPEND Struc to BAGDS.
       ENDLOOP.
*      Reading ITAB
*       WRITE : / , 'ITAB Begin : '    .
*       loop at BAGDS into Struc.
*         counter = counter + 1.
*         write : /,'Serial : ',counter.
*         write : / ,'PO : ',Struc-EBELN.
*         write : / ,'Vendor : ',Struc-LIFNR.
*         write : / ,'Vendor Name : ',Struc-NAME1.
*         write : / ,'Material : ',Struc-MATNR.
*         write : /,'Short Text: ',Struc-TXZ01.
*         write : / ,'Model : ',Struc-MATKL.
*         write : / ,'Model Desc : ',Struc-WGBEZ.
*         write : /,'GPM : ',Struc-SUBMI.
*         write : /,'Lot : ',Struc-CHARG.
*         write : /,'Received : ',Struc-RECV.
*         write : /,'Reversed : ',Struc-REVR.
*         write : /,'Delivered : ',Struc-DELV,/,/,/.
*       ENDLOOP.
* Call ALV Grid Viewer
*BREAK-POINT.
gr_Table[] = BAGDS[].
   CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
             I_STRUCTURE_NAME   = 'SBAGDS'
             IT_FIELDCAT          = gt_fieldcat[]
        TABLES
             T_OUTTAB                  = gr_Table.
Please Advise
Edited by: Sap Sap on Jul 27, 2009 12:18 PM
Edited by: Sap Sap on Jul 27, 2009 12:22 PM
Edited by: Sap Sap on Jul 27, 2009 12:22 PM

Hi,
The problem seems to be in your ALV grid display.
The reason must be your field catalog.
Just check your fieldcatalog.
The value in the fieldname field of the fieldcatalog should be same as the fieldname in your internal table and should be in capital letters.
Probably you must have mistyped some field.
Kinldy check.
Regards,
Ankur Parab

RUn time error while saving po    Field symbol has not yet been assigned.

Hi Experts,
I am getting abap dump while saving PO in ME21N plz seee the below dump plzzzzzzzzzzzzzzzzzzzzz help me
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          19.06.2009 11:24:46
Short dump has not been completely stored (too big)
Short text
     Field symbol has not yet been assigned.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLKKBL" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     You attempted to access an unassigned field symbol
     (data segment 106).
     This error may occur if
     - You address a typed field symbol before it has been set with
       ASSIGN
     - You address a field symbol that pointed to the line of an
       internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "GETWA_NOT_ASSIGNED" " "
    "SAPLKKBL" or "LKKBLF99"
    "GEN_FIELD_OUT2"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
em environment
SAP-Release 700
Application server... "gplqty"
Network address...... "128.12.0.19"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "GPLQTY"
Database type..... "MSSQL"
Database name..... "GPQ"
Database user ID.. "gpq"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 4 2008 02:33:25"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 172
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
   NT 6.0"
Memory consumption
Roll.... 16192
EM...... 16759360
Heap.... 0
Page.... 237568
MM Used. 12036016
MM Free. 530432
er and Transaction
Client.............. 410
User................ "SAP_SUPPORT"
Language key........ "E"
Transaction......... "ME21N "
Transactions ID..... "9E955CDE97CBF1648B4C001A64C7B85A"
Program............. "SAPLKKBL"
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Information on where terminated
    Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
    The main program was "RM_MEPO_GUI ".
    In the source code you have the termination point in line 2908
    of the (Include) program "LKKBLF99".
Source Code Extract
Line SourceCde
2878       else.
2879         assign <fs11> to <field>.
2880         gs_fc = gs_sfc11.
2881       endif.
2882     when 012.
2883       if gs_out_flags-slave ne 'X'.
2884         assign <fm12> to <field>.
2885         gs_fc = gs_mfc12.
2886       else.
2887         assign <fs12> to <field>.
2888         gs_fc = gs_sfc12.
2889       endif.
2890     when 013.
2891       if gs_out_flags-slave ne 'X'.
2892         assign <fm13> to <field>.
2893         gs_fc = gs_mfc13.
2894       else.
2895         assign <fs13> to <field>.
2896         gs_fc = gs_sfc13.
2897       endif.
2898     when 014.
2899       if gs_out_flags-slave ne 'X'.

Hi,
this error occurs when you try to address a field-symbol before it has been assigned to a field or
the assignment has failed.
Use following code to remove this dump
Assign <mara-matnr> to <fs>.
if sy-subrc <> 0.
Error Message.
Endif.
Hope it helps,
Raj

FAGLL03 Special Field Values Do Not Display in Production

We are using the new GL in ECC 6. I have a strange problem where special fields that were added to the line item transactions display in dev and quality but not in production. Please read the steps that I have taken.
1. Using note 984305 we defined special field BSEG-MATNR using this path:
Financial Accounting (New)
General Ledger Accounting (New)
    Master Data
      G/L Accounts
        Line Items
          Define Special Fields for Line Item Display
This field (U_MATNR) displays correctly in FAGLL03.
2. I used note 1034354 to create an implementation of BAdI 'FAGL_ITEMS_CH_DATA. Then I
followed the documentation of the BAdI to create structure CI_FAGLPOSX within FAGLPOSX and added these fields:
Material Type: field MARA-MTART
Material Group: MARA-MATKL
I added code to method CHANGE_ITEMS to read for those fields. Here's part of the code:
* MARA - Get Material Type and Material Group
    SELECT SINGLE mtart matkl
      FROM mara
      INTO (wa_items-zzmtart, wa_items-zzmatkl)
      WHERE matnr = wa_items-u_matnr.
The values of these fields display correctly in development and quality, but they do not display in production.
3. When I debugged FAGLL03 in development I found that the value of U_MATNR was filled when I stopped at method CHANGE_ITEMS. However, when I debugged in production, U_MATNR was not filled. It had to be filled at a later time because the value appears on the report. In my code, I am using U_MATNR to find the values of material type and material group. Because U_MATNR doesn't have a value at that point in time in production, my code doesn't find material type or material group.
4. I contacted SAP and was instructed to use note 984305. I executed the function module
ITEM_STRUC_EXTENSION which did not help.
5 I also used note 205096 to execute report BALVBUFDEL, but this did not help either.
6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
7. I tried to compare configuration between development and production, but everything looked OK to me.
Has anyone had this problem? Any tips?
Brenda

Hi Brenda,
>
Brenda Bankert wrote:
> 6. At this point, SAP told me that it is a consulting issue. I'm not sure that it is because I'm using SAP solutions without modifying anything.
I have no idea except that you can make sure Include CI_FAGLPOSX is active as well as the including FAGLPOSX. And please check the transport protocol(s) if CI_FAGLPOSX is included. If you have any kind of error/warning in the import protocol, that may give you a hint.
If nothing helps, create a new sap support case and tell them you are using SAP solutions without modifying anything.
Regards,
Clemens

Making field mara-maktl not mandatory in mm02/mm01

Similar Messages

Maybe you are looking for