Remove mandatory field from transaction KRMI

Hi,
In transaction KRMI, there are fields material and plant.
Material is a mandatory field. However, the user wants to see all the materials for a plant - not specific materials. They only want to enter the plant.
Is it possible to have material as an un-mandatory field? What are my options? Is guixt a possible solution?
If nothing else works, I would have to rebuild the report or copy & customize it.
Let me know.
Thanks.

Hi John,
SAP GuiXT resides at the presentation layer and defines the layout of the R/3 screen by series of commands in SCRIPT file.
SAP GuiXT is not the correct solution in your case, as this is machine dependent and you need to provide SCRIPT on each and every user machine.This can be only done in case your client has already implemented it.
You should try to find Screen Exit , if the same is not avaliable then proceed with creation of Z transaction.
Hope you understand it.

Similar Messages

Remove Mandatory field from OAOA Transaction

Hi,
There is a field in OAOA transaction - Account determination under Asset Type window. This field has the mandatory with value.
I don't want that field as mandatory.
How to do it..

That's not possible and makes no sense.

Remove text field from Array via for loop

Hi,
i have a problem to remove text fields added via for loop.
That im doing is, via for loop im dynamically creating menu with 10 buttons.
Each button contain, dynamically created, background (shape) and text field.
And everything is fine.
But when im try to remove text fields then i got this error:
- Im using button to remove text fields - lang_btn.addEventListener(MouseEvent.CLICK, clickHandler);
ArgumentError: Error #2025: The supplied DisplayObject must be a child of the caller.
          at flash.display::DisplayObjectContainer/removeChild()
          at Loading_Img_fla::MainTimeline/xmlLoaded()
          at flash.events::EventDispatcher/dispatchEventFunction()
          at flash.events::EventDispatcher/dispatchEvent()
          at flash.net::URLLoader/onComplete()
In the script bellow marked with red is what should remove text fields from an Array, instead giving me error.
Here is my script
// Create for loop
for (var i:int = 0; i < 10; i++)
          for each (xml in listItems)
                    if (i == xml.attribute("Id"))
                              // Add MovieClip to stage to hold the data
                              addChild(lmHolder);
                              lmHolder.x = 0;
                              lmHolder.y = 0;
                              // Create new MovieClip to hold buttons
                              lmButtonsMCArray[i] = new MovieClip();
                              lmButtonsMCArray[i].buttonMode = true;
                              lmButtonsMCArray[i].mouseChildren = false;
                              lmButtonsMCArray[i].x = 20;
                              lmButtonsMCArray[i].y = 20 + btCount * buttonSpace;
                              // Add each button MovieClip to lmHolder MovieClip
                              lmHolder.addChild(lmButtonsMCArray[i]);
                              // Create Background to buttons
                              lmButtonsArray[i] = new Shape();
                              lmButtonsArray[i].graphics.beginFill(lmBgColor0, 1);
                              lmButtonsArray[i].graphics.drawRect(0, 0, 230, 85);
                              lmButtonsArray[i].x = 0;
                              lmButtonsArray[i].y = 0;
                              // <<-- Add Background shape to the buttons MovieClips
                              lmButtonsMCArray[i].addChild(lmButtonsArray[i]);
                              // Create a new array to preserve data from XML List
                              lmNameArrayEG = new Array();
                              lmNameArrayUS = new Array();
                              // Create local variable to hold
                              var lmTxtFieldContentUS:String;
                              var lmTxtFieldContentEG:String;
                              var lmTxtContent:String;
                              // If clicked button is EG then make array with Arabic text
                              // If clicked button is US then make array with English text
                              if (footer.lang_btn.langState == "EG")
                                        for each (var leftMenuName:XML in egLanguageList)
                                                  lmNameArrayEG.push(leftMenuName);
                                        lmTxtFieldContentEG = lmNameArrayEG[i];
                                        lmTxtContent = lmTxtFieldContentEG;
                              else
                                        for each (var leftMenuNameUS:XML in usLanguageList)
                                                  lmNameArrayUS.push(leftMenuNameUS);
                                        lmTxtFieldContentUS = lmNameArrayUS[i];
                                        lmTxtContent = lmTxtFieldContentUS;
                              // Setup new text field each time script is executed
                              lmTxtFieldsArray[i] = new TextField();
                              lmTxtFieldsArray[i].width = 110;
                              lmTxtFieldsArray[i].border = false;
                              lmTxtFieldsArray[i].wordWrap = true;
                              lmTxtFieldsArray[i].multiline = true;
                              lmTxtFieldsArray[i].selectable = false;
                              lmTxtFieldsArray[i].embedFonts = true;
                              lmTxtFieldsArray[i].antiAliasType = AntiAliasType.ADVANCED;
                              lmTxtFieldsArray[i].autoSize = TextFieldAutoSize.CENTER;
                              lmTxtFieldsArray[i].text = lmTxtContent.toUpperCase();
                              lmTxtFieldsArray[i].x = 10;
                              lmTxtFieldsArray[i].name = "lmTxtFieldName" + i;
                              // <<-- Add Text fields to the Movie Clip
                              lmButtonsMCArray[i].addChild(lmTxtFieldsArray[i]);
                              // If clicked button is EG then set Arabic text format, and make array with Arabic text fields
                              // If clicked button is US then set English text format, and make array with Egnlish text fields
                              if (footer.lang_btn.langState == "EG")
                                        lmTxtFieldsArray[i].setTextFormat(txtFormat_lm_eg);
                                        // Make array from text fields;
                                        pushEgTFintoArray.push(lmTxtFieldsArray[i]);
                              else
                                        lmTxtFieldsArray[i].setTextFormat(txtFormat_lm_us);
                                        // Make array from text fields;
                                        pushUsTFintoArray.push(lmTxtFieldsArray[i]);
                              // If clicked button is EG then loop thrue the for loop and remove English text fields from array
                              // If clicked button is EG then loop thrue the for loop and remove Arabic text fields from array
                              if (footer.lang_btn.langState == "EG")
                                        for (var rNr_us:Number = 0; rNr_us < pushUsTFintoArray.length; rNr_us++)
                                                  //remove the text field array from the display
                                   removeChild(pushUsTFintoArray[rNr_us]);
                                        //clear the array
                                        pushUsTFintoArray = [];
                              else
                                        for (var rNr_eg:Number = 0; rNr_eg < pushEgTFintoArray.length; rNr_eg++)
                                                  //remove the text field array from the display
                                   removeChild(pushEgTFintoArray[rNr_eg]);
                                        //clear the array
                                        pushEgTFintoArray = [];
          btCount++;

it looks like those tf's are children of lmButtonsMCArray[i], not the current scope. use:
if (footer.lang_btn.langState == "EG")
                                        for (var rNr_us:Number = 0; rNr_us < pushUsTFintoArray.length; rNr_us++)
                                                  //remove the text field array from the display
                                    lmButtonsMCArray[rNr_us].removeChild(pushUsTFintoArray[rNr_us]);
                                        //clear the array
                                        pushUsTFintoArray = [];
                              else
                                        for (var rNr_eg:Number = 0; rNr_eg < pushEgTFintoArray.length; rNr_eg++)
                                                  //remove the text field array from the display
                                    lmButtonsMCArray[rNr_eg].removeChild(pushEgTFintoArray[rNr_eg]);
                                        //clear the array
                                        pushEgTFintoArray = [];

Disable or Remove some field from User Profile in Personalize iView

Hi All,
I have a requirement to Disable one field and Remove one field from User Profile in Personalize iView.
i want to disable Activate Accessibility Feature field and Remove Language field.
How to archive this.
Thanks and Regards
Trilochan

Hi,
You can use [Personalization|http://help.sap.com/saphelp_nw70/helpdata/en/42/ed3ce7f8593eebe10000000a1553f7/frameset.htm] to do this :
1. logon as an admin and navigate to Portal Content > Portal Users > Standard Portal Users and open Every User Core Role
2. right click on User Profile and select edit
3. click on the Preview button then right click + CTRL on the iView and personalize the User Profile iView
That's it.
Regards,
Pierre

What are the Mandatory Fields in Transaction ME51

Hello Seniors,
I have a requirement about purchase order creation. In this process, I am using the BAPI named " BAPI_PO_CREATE1 ". I have passed all the fields but when I debug and look into the internal tables, I couldn't find certain records. I even debugged " bapiret2" and I see an error which reads "" All mandatory fields are missing"". I have even created a PO in ME51 and found out the mandatory fields but in vain. BAPIRET2 still says, there are some more mandatory fields missing. I need to know what are all the mandatory fields to create a Purchase order using TCODE - ME51.
Your reply is most awaited and rewarded.
Thanks and Regards,
MARKIV

hi ,
Functionality
Function module BAPI_PO_CREATE1 enables you to create purchase orders. The BAPI uses the technology behind the Enjoy purchase order transaction ( ME21N).
Alternatively, the IDoc type PORDCR1 is available. The data from this IDoc automatically populates the interface parameters of the function module BAPI_PO_CREATE1.
Functionality in Detail
Authorization
The following authorization objects are checked when an Enjoy purchase order is created (activity 01):
M_BEST_BSA (document type in PO)
M_BEST_EKG (purchasing group in PO)
M_BEST_EKO (purchasing organization in PO)
M_BEST_WRK (plant in PO)
Controlling adoption of field values via X bar
For most tables, you can determine via your own parameters in the associated X bar in each case (e.g. PoItemX) whether fields are to be set initial, values inserted via the interface, or default values adopted (e.g. from Customizing or master records) (for example, it is not mandatory to adopt the material group from an underlying purchase requisition - you can change it with the BAPI).
Transfer
Header data
The header data of the Enjoy purchase order is transferred in the table PoHeader.
Item data
The item data of the Enjoy purchase order is stored in the table PoItem (general item data). The delivery schedule lines are stored in the table PoSchedule.
Use the table PoAccount to specify the account assignment information. If account assignments have been specified for services and limits, you show the relevant account assignment line in PoAccount in the table PoSrvAccessValues via the package number of the service or the limit.
Services and limits
Services, free limits and limits with contract reference can be specified in the tables PoServices, PoLimits, and PoContractLimits.
Conditions
Conditions are transferred in the table PoCond; header conditions in the table PoCondHeader. Price determination is reinitiated via the parameter CALCTYPE in the table PoItem.
Vendor and delivery address
The vendor's address can be specified individually in the table PoAddrVendor; the delivery address in the table PoAddrDelivery. If you do not make any individual specification, the fields will be populated via the central address managementfacility.
Note
In this method, the following restrictions apply with regard to addresses:
Addresses can only be created with this method - they cannot be changed. You can only change address data with the method BAPI_ADDRESSORG_CHANGE.
When you create addresses, they are not checked by the method. An Enjoy purchase order may therefore contain faulty address data.
Partner roles
The partners can be maintained individually via the table PoPartner (with the exception of the partner role "vendor").
Import/export data
Import/Export data can be specified per item in the table PoExpImpItem. Foreign trade data can only be transferred as default data for new items.
Texts
Header and item texts can be transferred in the tables PoTextHeader and PoTextItem. Texts for services are imported in the table PoServicesText.
Version Management
You can make use of the Version Management facility via the table AllVersions.
Return
The PO number is returned in the parameter ExpPurchaseOrder. In addition, all information except the service and export/import tables is placed in the output structures.
Return messages
Messages are returned in the parameter Return. This also contains information as to whether interface data has been wrongly or probably wrongly (heuristical interface check) populated. If a PO has been successfully created, the PO number is also placed in the return table with the appropriate message.
Example
Example of population of BAPI interface in the Function Builder
Parameter: POHEADER
COMP_CODE = 1000
DOC_TYPE = NB
ITEM_INTVL = 00001
VENDOR = 0000001000
PMNTTRMS = 0001
PURCH_ORG = 1000
PUR_GROUP = 001
CURRENCY = EUR
Parameter: POHEADERX
COMP_CODE = X
DOC_TYPE = X
ITEM_INTVL = X
VENDOR = X
PMNTTRMS = X
PURCH_ORG = X
PUR_GROUP = X
Parameter: POITEM
PO_ITEM = 00001
MATERIAL = 100-100
PLANT = 1000
STGE_LOC = 0001
QUANTITY = 15.000
TAX_CODE = V0
ITEM_CAT = 0
ACCTASSCAT = K
Parameter: POITEMX
PO_ITEM = 00001
MATERIAL = X
PLANT = X
STGE_LOC = X
QUANTITY = X
TAX_CODE = X
ITEM_CAT = X
ACCTASSCAT = X
Parameter: POSCHEDULE
PO_ITEM = 00001
SCHED_LINE = 0001
DELIVERY_DATE = 02.12.2002
QUANTITY = 6.000
PO_ITEM = 00001
SCHED_LINE = 0002
DELIVERY_DATE = 03.12.2002
QUANTITY = 5.000
PO_ITEM = 00001
SCHED_LINE = 0003
DELIVERY_DATE = 04.12.2002
QUANTITY = 4.000
Parameter: POSCHEDULEX
PO_ITEM = 00001
SCHED_LINE = 0001
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0002
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
PO_ITEM = 00001
SCHED_LINE = 0003
PO_ITEMX = X
SCHED_LINEX = X
DELIVERY_DATE = X
QUANTITY = X
Parameter: POACCOUNT
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = 15.000
GL_ACCOUNT = 0000400000
COSTCENTER = 0000001000
CO_AREA = 1000
Parameter: POACCOUNTX
PO_ITEM = 00001
SERIAL_NO = 01
QUANTITY = X
GL_ACCOUNT = X
COSTCENTER = X
CO_AREA = X
Parameter: POCOND
ITM_NUMBER = 000001
COND_ST_NO = 001
COND_TYPE = PB00
COND_VALUE = 79.900000000
CURRENCY = EUR
CURRENCY_ISO = EUR
COND_UNIT = KG
COND_P_UNT = 1
CHANGE_ID = U
Parameter: POCONDX
ITM_NUMBER = 000001
COND_ST_NO = 000
ITM_NUMBERX = X
COND_TYPE = X
COND_VALUE = X
CURRENCY = X
CHANGE_ID = X
Parameter: POPARTNER
PARTNERDESC = OA
LANGU = EN
BUSPARTNO = 0000001100
PARTNERDESC = GS
LANGU = EN
BUSPARTNO = 0000001200
PARTNERDESC = PI
LANGU = EN
BUSPARTNO = 0000001000
Help in the Case of Problems
1. Note 197958 lists answers to frequently asked questions (FAQs). (Note 499626 contains answers to FAQs relating to External Services Management.)
2. If you have detected an error in the function of a BAPI, kindly create a reproducible example in the test data directory in the Function Builder (transaction code SE37). Note 375886 tells you how to do this.
3. If the problem persists, please create a Customer Problem Message for the componente MM-PUR-PO-BAPI, and document the reproducible example where necessary.
Customer Enhancements
The following user exits (function modules) are available for the BAPI BAPI_PO_CREATE1:
EXIT_SAPL2012_001 (at start of BAPI)
EXIT_SAPL2012_003 (at end of BAPI)
The following user exits (function modules) are available for the BAPI BAPI BAPI_PO_CHANGE:
EXIT_SAPL2012_002 (at start of BAPI)
EXIT_SAPL2012_004 (at end of BAPI)
These exits belong to the enhancement SAPL2012 (see also transaction codes SMOD and CMOD).
There is also the option of populating customer-specific fields for header, item, or account assignment data via the parameter EXTENSIONIN.
Further information
1. Note 197958 contains up-to-date information on the purchase order BAPIs.
2. If you test the BAPIs BAPI_PO_CREATE1 or BAPI_PO_CHANGE in the Function Builder (transaction code SE37), no database updates will be carried out. If you need this function, please take a look at Note 420646.
3. The BAPI BAPI_PO_GETDETAIL serves to read the details of a purchase order. The BAPI cannot read all details (e.g. conditions). However, you can use the BAPI BAPI_PO_CHANGE for this purpose if only the document number is populated and the initiator has change authorizations for purchase orders.
4. Frequently used BAPIs for purchase orders are BAPI_PO_CREATE, BAPI_PO_CREATE1, BAPI_PO_CHANGE, BAPI_PO_GETDETAIL, BAPI_PO_GETITEMS, BAPI_PO_GETITEMSREL, and BAPI_PO_GETRELINFO.
5. For more information on purchase orders, refer to the SAP library (under MM Purchasing -> Purchase Orders) or the Help for the Enjoy Purchase Order, or choose the path Tools -> ABAP Workbench -> Overview -> BAPI Explorer from the SAP menu.
regards
reena

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
To delete characteristics or value fields, perform the following activities:
1. Delete the corresponding characteristics and value fields from Customizing in all clients (this includes forms, reports, planning layouts, and so forth). To locate characteristics and value fields, use the appropriate where-used list in the Customizing Monitor. You can access it by choosing Tools -> Analysis -> Check Customizing Settings. You can jump directly from the where-used list to the relevant Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the operating concern before making any deletions, effect those changes and save the data structure.
4. In order to be able to select the fields of the data structure, choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking whether the operating concern contains any data and whether the fields to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the re-activation. If the operating concern does not contain any data or does not require the database system to be converted, the tables are activated. You are then able to activate the environment for the operating concern. In this case, the following activities no longer apply.
If the operating concern already contains data, a system message tells you that the database needs to be converted. If you proceed, an activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can be converted. In this case, you should answer "No" to the next prompt, which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted is shown for this. If the tables only contain a small amount of data (less than 10 000 records), then all the tables can be converted in one job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs. However, you should ensure that table CE4xxxx (where xxxx = operating concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during the conversion.
A copy of the table is generated during the conversion. The database system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function. You can display the current status of the conversion by selecting the "Refresh" icon. Tables disappear from the list once they have been converted sucessfully. If a conversion is taking a while, it is also possible to leave the transaction. You can then continue the conversion using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services -> Jobs.
Using the database utility transaction. You access this by choosing Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating concern during operating concern maintenance. You need to activate all tables after conversion.
11. To analyze errors that have occurred during the conversion, you can use the database utility transaction by choosing Extras -> Logs. The log has the same name as the conversion job: TBATG-date. You can also restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application help while still in the above transaction.
12. Once you have activated all the tables in the operating concern, generate the operating concern environment from within operating concern maintenance.
You can then use the operating concern again.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

How we remove some fields from SAP standard one's

Hi,
i am very new to SAP SD .if the client do not want some fields from standard one's how we can remove those fields.(example u take Standard sales order).

HI, you cannot hice many fields in SAP, since they all need for something.
try to explain this to your customer; furthermore many fields are filled form the master data so the users don't have do mind of them.
Anyway you can alter the screens using the transaction variants: go to IMG
Spro: SAPNetwaever->general settings->Field Display Characteristics->Configure Application Transaction Fields
Reward if helpful
Regards
Roberto

How to remove mandatory field for Last Name in Personal Data Editing Screen

Hello All,
CUrrently we are using BP_ ERP5ESS1.31 SP5 & SAP_ESS 603 SP5.
All my ESS Services are Displaying fine and working from Portal.I am having the requirement like I need to make Last Name as Non-Mandatory field in Personal Data. While Editing the PD Screen, there i will find the * mark for Last Name filed, i checked through the Global Personalization Make as Mandatory is Not Personalized its showing, i think its defualt prpoerty,so i am unable make any changes from Portal w.r.t Global Personalization.
I checked in SPRO-- Personal Admin> Custmomizing User Interfaces>Change Screen Modifications, there i find the respective Module pool for those Infotypes and country Specific..
I cheked forModulePool MP000200--> P0002 and Variable Key-40(For India) P0002 - NACHIN -- LastName only OF Radio Button is Selected all other Rado buttons are not selected.
I Checked in V_T588MFPROPS view there for 0002 Infotype P0002 -- NACHN Mandatory check box is Checked all other check boxes are Unchecked.
How to make that Last Name field as Non-Mandatory in Personal Data Edit Screen, where i need to make the changes.'
Please list out the Steps..Where i need to do the configuration. And i assigned all the required ESS roles on the backend.
Thanks in Advance
Adapag

Hi,
I don't think supressing through Global Personalization will change the business logic. Within the Business Logic it checks for the mandatory field.
After the changes I guess you need to make the changes accordingly.
The below link might be of some help.
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=profile&title=ESSPersonalInformationUIenhancementwithoutmodification&decorator=printable
Please correct if I am wrong.
Cheers-
Pramod

Hide/remove the fields from the time accounts table on the screen of approval leave request

Hi,
i want to remove or hide the fields from the following table .
is there anybody who know how to do? help me pls!
Thanks in advance

it shoukd be done by coding only ie NWDI and no config is available http://scn.sap.com/thread/1752655

Removing mandatory field checks

Hi all
We are working on ESS/MSS packages customization and we have a requirement where in we need to make a mandatory field in one of the screens, non-mandatory e.g. zip code in address information. I have the Webdynpro code of mentioned screen in my NWDS. Any pointers are welcome.
with thanks
amit

Hi amit,
The state of a webdynpro element can be set using
void setState(WDState value) in the implementation of your view.
Check the
IWDAbstractInputField
in
<a href="https://help.sap.com/javadocs/NW04S/current/wd/index.html">WDAPI</a>
Attributes available
static WDState NORMAL
The normal state of a UI element.
static WDState REQUIRED
Indicates that a UI element must provide a value for performing a certain action.
Thanks,
Swathi

Updating 'SEGMENT' field from transaction FB60 using FAGL_DERIVE_SEGMENT

In our project we are using BADI FAGL_DERIVE_SEGMENT to automatically determine the field 'SEGMENT' from FB60 transaction.
This problem only occurs when the field 'Segment' has been updated, because upon creation the value is filled and calculated correctly by the BADI. But it seems that on modification, the BADI is not being called, and therefore the field remains unchanged.
(This only happens in the table control, because when double-clicking on the line we see that the value is correctly updated)
Does anyone know any OSS note or any solution (maybe another BADI or configuration) to always have the value updated in the table control?
Thanks in advance!
Regards,

Hi John,
Through inbound IDOC, if the material already exists then material no will also be passed.
Use WE19. and give the value for MEINS and check in debug mode.
Regards
Arun

EDI Outbound IDOC Remove unused fields from segment

Hi All,
I am configuring a outbound idoc scenario for Message type ORDERS. The basic type for this message type is ORDERS05.
The segment E1EDKA1 has 44 fields, I need only the first field and the last field of this segment.
How do I remove the unused fields in this segment ? I Tried BD56 and BD32 But they are for removing the complete segment and so does not serve my purpose.
Any pointers to this issue is appreciable .
Regards,

Hi,
Segmetns of standard message types can be deleted from BD53. But I don't think deleting fields would be possible from segments of standard idoc type. What you can do is you can create your own custom idoc type with the fields you want and allign it with the standard message type ORDERS. This should solve your purpose.
BR,
Atanu Mukherjee

TS01: Remove other flows from transaction and save

Dear Experts,
TRM has been customized whenever a new transaction is created (using TS01) and a specific Business Partner chosen (Counterparty), additional flows for commissions (0301 u2013 flow type) and transfer fees (0302 u2013 flow type) are automatically generated based on IMG u201CDefine Derivation Procedures and Rulesu201D and its assignment of u201Cderived flowsu201D of the specific BP.
For a specific transaction our customer wants to remove the second flow 0302 u2013 Transfer fees although its deal has been performed with the same Counterparty that in its derivation rules include this flow (0302 u2013 Transfer fees). The business scenario is that this counterparty has always derived flows (Commissions and Transfer fees) but for this single one transaction it does not charge transfer fees.
When I create the transaction (TS01), after filling the payment amount, I move to u201COther Flowsu201D tab. In this the two flows have been automatically created. Then I choose the second line with 0302 flow type and I choose u201CDelete Rowu201D. Although initially the line disappears from the u201COther flowsu201D list, when I press Enter or Save the transaction the line with 0302 flow type reappears. It seems as I cannot remove the flow.
Additionally I cannot change the amount of the flow!
Does anyone know how to remove the flow and save the transaction and /or change the proposed by the system amount?
Thank you, I would appreciate any help.

Hi,
For transaction derived flows, you can only change the amount but cannot remove the item as it is derived by default. In case for a single transaction you don't want the derived flow, you can remove it from the standing instructions of the counterparty and then create the transaction and then add the instruction back.
Or you have to add the same flow in the reverse direction for the same amount in other flows so that is gets nullified.
Regards,
Ravi

Remove Mandatory field in Cost center master data

Dear All,
I want to remove the mandatory person responsible in the cost center master data. How to do this
Regards
Vasantha

hi Vasantha,
as far as I know, this is not possible. If a field is mandatory or not in cost center master data is determined by the system.
hope this helps
ec

Removing text field from po

hi gurus
i want to keep
in header texts
1) header note
2) delivery note
3) payment terms
in item text only item text
all other texts in header and item level i want to remove can i do it so
so that other texts get supress
plz help

If you want to remove from the transaction screen use the following path
(generally not advisable to delete the standard configuration delivered for text types)
SPRO->Materials Management->Purchasing->Purchase Order->Texts for Purchase Orders->Define Text Types for Purchase Order Texts.
In this you can keep the texts you want and delete the rest. Similarly, you can do the same for item texts.
If your requirement is to delete from the print layout, do the following:
SPRO->Materials Management->Purchasing->Messages->Texts for Messages->Define Texts for Purchase Orders. In this place, you configure only the text types which are needed for your print.

Remove mandatory field from transaction KRMI

Similar Messages

Maybe you are looking for