Mandatory Field in Journals

Hi,
I would like to make Trading Partner as a Mandatory field for a particular GL account when entering FB50. I have checked OBC4 but could not find the Field so that i can mark as Mandatory. Can anyone suggest.
Thanks
Imran

Dear:
              Use SHDO if you want it to be mandatory for every posting made through FB50 but if your requirement is restricted to some specific GL posting then you need to create a validation in your system using T Code GGB0. You can create a GL set using T Code GS01 and use this set in your validation for making it mandatory for some GL Accounts. Don't hard code the GLs in your validation as if you use set then you get the flexibility to remove/add the GLs from the set. You can also create another set for Company Codes and use it in your validation. This gives you an additional flexibility to make this mandatory for any Co. Code you want. I hope this will resolve your issue.
Regards

Similar Messages

  • Mandatory field - Disribution rule

    Hi Experts,
    My client needs the requirement that while journal entry screen distribution rule field have set as mandatory field.
    how its possible ?
    Using Query its possible, but i want some other work around ?
    Regards,
    Sanju M S

    Hi
    Use this in SP_Transaction Notfication: if they not selected the DR it will not allow to post in system.
    set ANSI_NULLS ON
    set QUOTED_IDENTIFIER ON
    go
    ALTER proc [dbo].[SBO_SP_TransactionNotification]
    @object_type nvarchar(25),
    @transaction_type nchar(1),
    @num_of_cols_in_key int,
    @list_of_key_cols_tab_del nvarchar(255),
    @list_of_cols_val_tab_del nvarchar(255)
    AS
    begin
    declare @error  int                    
    declare @error_message nvarchar (200)           
    select @error = 0
    select @error_message = N'Ok'
    IF (@transaction_type = 'A' or @transaction_type = 'U') AND @object_type = '30'
    BEGIN
    if Exists (SELECT T0.[TransId] FROM OJDT T0  INNER JOIN JDT1 T1 ON
    T0.TransId = T1.TransId where T1.ProfitCode is null and T0.[TransId] = @list_of_cols_val_tab_del)
         begin
              SET @error = 10
              SET @error_message = N'Profit Centre is Null'
         end
    END
    select @error, @error_message
    end
    Wish u happy new year
    Giri

  • What are the mandatory fields while creation of material master in differen

    what are the mandatory fields while creation of material master in different views?

    Hi Gopi,
      This is purely depends on the function configuration, which would be done MM consultants.  Kindly check with them.
    thanks & regards
    Kishore Kumar Maram

  • Dynamic mandatory field error message is not getting displayed in webui

    Hi,
    In Appointment if the importance is HIGH i made Location as mandatory.For this i enhanced BT126H_APPT/ApptDetails. In the get_p_location() method of BTACTIVITYYH i have written the code.
    Now the problem is Error message for this dynamic mandatory field is not getting displayed in webui.
    I debugged in DO_FINISH_INPUT error message is getting generated but it is not getting displayed in ui.
    Can anybody tell where the problem is?
    Thanks,
    Hari.

    Hi Hari,
    Really sorry do not know how to convert this nug file to text
    How ever quick solution for your problem would be just keep your validation in 'DO_VALIDATE_INPUT' method of the view controller.
    Means even if the User clicks on SAVE , Since it fails here , it would not allow you to go further.
    Thanks,
    Rajesh P

  • Mandatory fields while using Group chart of accounts

    Hi,
    Which are the mandatory fields while maintaining GL accounts in FS00 if i am using Group chart of accounts.
    And how attached these group chart of accounts gl to the operational chart of account GL.
    raj

    Hi,
    the assignment from operational chart of accounts to group chart of accounts is done in OB13. Follow the steps in Customizing IMG FIn. Acc. (new) / Consolidation preparation (new) / General specifications / G/L and FS Charts of accounts...
    Best regards, Christian

  • What are all the mandatory fields of the BAPI_PO_GETDETAIL?

    Hi friends,
    I am new to XI. I am using the "BAPI_PO_GETDETAIL1" in my scenario to get details of a particular Purchase Order. Can you tell me the mandatory fields of this BAPI?
    Where should i look to identify the mandatory fields of a BAPI?
    Thanks.
    Senthil Nathan.

    Hi you can see this in SE37 under the Import Tab. Here you see that the only mandatory input field is PURCHASEORDER. So if you provide the purchaseorder number you get alle the details for that.
    Kind regards
    Mikkel

  • What are the Mandatory fields????

    Hi.... Experts...
       Please spend your valueble time for me.... I can get back to you with 10 points....
    Here I got a requirement to create contract with VA41 transaction...
    But I am in confusion with feilds which should be must record...
    Please guide me on mandatory fields of VA41 transaction....
    Thanks,
    Naveen.I

    Hi,
    When ever you want to know the required fields for any transaction just try to run the Transaction In SHDB in forgroud mode with a recording name.
    You will easily get to know the required fields to be entered for a given transaction.
    Sometimes when we run this VA41, eventhough some fields are not mandatory we dont pass them but we willnt b able to create the document eventhough some fields are not mandatory to fill> To have the clear idea abt the manadotry fields try to run in SHDB.
    for this VA41, ther mandatory fields are-
    contract type (VBAK-AUART)
    Sales Area is a combintaiotn of SAles Org, SAles divnsion, Distirbution channel hende all 3 are required to be filled.
    1st screen-
    Sales Area(VBAK-VKORG)
    Division(VBAK-SPART)
    D.Channel(VBAK-VTWEG),
    2nd screen-
    Customer code(kunnr),
    Contract validity,
    material code(matnr),
    quantity
    plant(werks).
    Best Wishes,
    Chandralekha
    Edited by: Craig Cmehil on Jun 30, 2008 11:24 AM

  • 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

  • Mandatory Field in ALV Grid

    Hello,
    i've a editbale alv grid.
    Is it possible to set a field/colum as mandatory field?
    Best regards,
    TomSd

    Hi,
    Have a look at the report BCALV_EDIT_03.
    In this report the program logic is such that if the user enters an incorrect value an error is displayed.
    Instead you can check if the field of your ALV filelds are null and validate them accordingly.
    Regards,
    Sandeep

  • Mandatory field validation on Page links.

    We have created a Portal application where we included different applications as taskflows. We have also created a tabbed interface which helps us to communicate from one task flow to another taskflow. When we are in one page of taskflow and try to move to another page of different taskflow using tabbed interface we receive mandatory field validation error which prevents us to move to any other page until we fill all the mandatory fields. We need to move to different page of taskflow by using the tabbed interface even without filling all the necessary mandatory fields. Can anyone help us to resolve this issue as this is very important for our project.

    <b>Layout</b>
    <%@page language="abap" %>
    <%@extension name="htmlb" prefix="htmlb" %>
    <htmlb:content design="design2003" >
      <htmlb:page title="Check Pernr " >
        <htmlb:form>
          <htmlb:textView text   = "Personnel No."
                          design = "EMPHASIZED" />
          <htmlb:inputField id    = "pernr"
                            value = "<%= lv_pernr %>" />
    <%
    if lv_no_pernr = 'X'.
    %>
    <script language="Javascript">
    alert ("Personnel no. is not Valid")
    </script>
    <%endif.%>
       </htmlb:form>
      </htmlb:page>
    </htmlb:content>
    <b>ONINPUTPROCESSING</b>
    DATA: l_pernr TYPE persno.
      DATA: data TYPE REF TO cl_htmlb_inputfield.
      data ?= cl_htmlb_manager=>get_data( request = runtime->server->request
                                             name     = 'inputField'
                                             id       = 'pernr' ).
      IF data IS NOT INITIAL.
        l_pernr = data->value.
      ENDIF.
    CLEAR lv_no_pernr.
    SELECT SINGLE pernr FROM pa0000 INTO l_pernr WHERE pernr EQ lv_pernr.
    IF sy-subrc NE 0.
      lv_no_pernr = 'X'.
    ENDIF.
    <b>PAGE ATTRIBUTES</b>
    lv_no_pernr     TYPE     FLAG
    lv_pernr     TYPE     PERSNO
    hope this helps.
    A

  • How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice

    Hi,
    Kindly solve, How to put Sales employee (Splcode) Mandatory Field, when adding A/R invoice.
    Regards,
    Rajeev.

    Follow this step..
    1. In SQL Server, go to the SAP B1 Database you're using. 
    2. then on the Object Explorer , go to Database Folder, explode the SAP DB->Programmability->Stored Procedures->SBO_SP_TransactionNotification * the only Stored Procedure that is allowed to be edited. Just right click and modify
    3.  Try to paste this -> and click F5
    If
    @object_type ='13' and @transaction_type in ('A','U')
    Begin
    If EXISTS
    select DocEntry from ONIV
    Where DocEntry = @list_of_cols_val_tab_del
    and  SlpCode<>'-1'
    Begin
    set @error_message = 'Please select the Sales Employee'
    set @error = 1
    END
    END
    Regards
    Kennedy

  • Check for mandatory fields while creating EP users using code .. :|

    Hello All,
    I have a code using which I can create user accounts/EP users on Portal, am working on EP6 SP9 & SP12.
    <u>My query</u>:
    1. <i>From Portal's perspective</i> -> While creating EP users, there are few mandatory fields like user-id, FirstName, LastName, Email-id and Password. If any of the above fields is null/empty, Portal would give us an error message.
    2. <i>From coding perspective</i> -> Here, only the user-id is required. Even if I do not enter/fill any of the above mentioned mandatory fields (except user-id), user account is created.
    In case wherein FirstName/LastName is not mentioned, Portal shows the userid in the Welcome Frame, i.e. Welcome <user-id>. Tried this by commenting the statements contains the methods related to setting/accepting FirstNme and LastName of user.
    <b>I want to know if this is all rite?
    If no, then please guide me as to how can I set mandatory fields in my code.</b>
    Awaiting Reply.
    Thanks and Warm Regards,
    Ritu R Hunjan

    Hi Ritu,
    >>please guide me as to how can I set mandatory fields in my code??
    In ur jsp file or in the controls code add the following attribute
    <hbj:label id="userIdLabel"
               text="User ID"
               labelFor="userIdInput"
               design="HEADER3"
               required="true"/>
    and to check the mandatory entry for that field do this in the submit button
    <hbj:button id="insert"
                text="Submit"
                design="emphasized"
                onClick="save"
                onClientClick="if(!isMandatory()) htmlbevent.cancelSubmit=true;;"/>
    and in the javascript write the client validation code.
    Hope this helps.
    Regards,
    Joshua Kiran

  • Credit memo and mandatory fields in Sales order

    Dear all,
    I have 2 problems, hoping these are not too basic questions I'm asking here.
    1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
    The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
    Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
    2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
    Many thanks!
    Best regards.

    Hi There,
    > 1). I have created a sales order for credit memo's and I'm using the standard billing type G2.
    > The amounts are negative in the order & in the billing document, however, when transferring to FI, it is posted as a normal invoice (Debit customer) instead of credit memo.
    >
    > Where are the posting keys defined or where do you determine which kind of posting will happen in FI based on the billing document?
    This is the standard SAP behavior. Simple thing, All the values are negative so when it will post to FI
    It will be like
    Dr  Customer Invoice amount ( which is negative ) so end result is +ve. ( as Debit is -)
    I hope its understandable.
    For example:
    While creation of simple invoice say of 1000 $
    Entries were Dr Customer 1000 $
                         Cr Revenue    1000$
    Now After Credit memo
                        Dr Customer    -1000 $
                         Cr Revenue    -1000 $
    Which will nullify each other.
    > 2). When creation a sales order (VA01), the sales office and sales group should be mandatory fields. What is the best way to do this? Or is the only option to go via the document completeness check?
    The best way is to include these two fields in the Sales order incomplete procedure in OVA2. Put Error/warning as required by you.
    Thanks,
    Raja

  • User Created in OIM 11.1.1.5 with null value for mandatory field.

    Hi,
    We had updated one UDF as mandatory field on OIM user form. We can see the * in front of that field. Now if we create the user using web console (Using UI), we are not able to create the user without giving some value in that UDF as it is mandatory. However if we created the user with UDF value as null using Trusted recon, User sucessfully created in OIM. I had attached the screen shot for that user which create in OIM with UDF value as null.
    Is any thing else also need to do to make UDF as mandatory field.
    Regards,
    Sid

    I am not sure this is a bug. Such mandatory checks will often only apply to administrative changes from the GUI. You may not always be able to enforce the same quality of data in reconciled data as you wish to impose for changes made through OIM, and it may prove an issue in some cases if such users could not be reconciled. In this case the use will go into OIM, but you will be forced to populate a value in the mandatory field if you later try to update them in OIM.

  • What and Which are the Mandatory fields in a Purchase Order?

    Please advise how I can check what the Mandatory fields are in a purchase order and which fields are not Mandatory ?
    Also, Please advise where this information can be found in the manual?
    Thanks in advance.
    Edited by: Darpal Thiarha on Feb 26, 2008 3:49 PM

    Hi,
    mandatory fields are:
    vendor
    docdate
    delivery date
    and other fields you may test in sbo_transactionnotification procedure.
    I don`t think that this is written in manual, you have to test to add the document with few fields filled and check it.
    Petr

Maybe you are looking for