Mandatory field set up for Profitable segment entry

Dear All,
Is there any way to set up Customer as mandatory field in profitable segment while manually posting  to GL for which Profitable segment is required.
Thanks,
Ram

Hi Ram,
You could try to use Enhancement COPA000 for this requirement.

Similar Messages

  • Required a customer field(located in the profitability segment box) as mand

    our client is requested  that the customer field (located in the Profitability Segment box) be a mandatory field for GL accounts which are getting posted directly from FI. This field is needed so that proper reporting can be generated for bad debt and product liability claims. Currently this field is not a mandatory when making journal entries, so there were some postings happened with out customer field. Due to this we are unable to extract exact values in CO-PA reports . Please can some one help me on this and explain the process and settings for this??
    Thanks in advance.
    Regards,
    Venkat

    Hi Eli,
    I have posted note to SAP and i got the below reply from them.
    Get this functionality you should change
    the coding of form DERIVE_CRITERIA_EXTENDED from include RKEVRK2L after
    uninstallation of note 115500(in case you have installed) like this:
    Im Dialogfall (Kontierungspopup) Verprobung ob für Feld
    Mußeingabe erforderlich (Merkmalsgruppe!)
    (nicht f. Faktura, da dort keine Fehlermeldung moeglich)
    if ( xt_criteria-field is initial
    BEGIN OF DELETION *****
    and xt_criteria-status eq '2'
    and not is_status_flags-dialog is initial ) .
    perform send_message using 'KE' 'E' '494'
    END OF DELETION *****
    BEGIN OF INSERTION *****
    and xt_criteria-status eq '2' ) .
    data: l_mtyp type c.
    if not IS_STATUS_FLAGS-DIALOG is initial.
    l_mtyp = 'E'.
    else.
    l_mtyp = 'W'.
    endif.
    perform send_message using 'KE' l_mtyp '494'
    END OF INSERTION *****
    xt_criteria-fieldname
    is_cobl-vorgn
    i_char_group
    endif.
    Afterwards you have to run function module RKE_GENERATE_INTERFACE_ACT
    for your operating concern to update the generated program RK2LXXXX.
    Thanks & Regards,
    Venkat

  • How to remove the mandatory field setting in output control

    Hi everybody,
    While printing a Payment Voucher through F-58 and FBZ5(reprint), there are two output devices, the first one is - printer for forms and second is - payment advice printer.
    In our case we have configured the cheque printing and payment voucher printing seperately. The cheque goes to first printer(kept mandatory field) and the payment voucher goes to second printer. One of our plant does not print the cheque from SAP, they only print the payment voucher because the cheque is manually prepared. How do I avoid the cheque printing. Is there any way out to print only the payment voucher through F-58 and FBZ5
    Please guide me how to tackle it or how to remove the mandatory field setting in the output control screen?
    Regards
    Paul

    Hi
    As of my understanding, there is no relation ship between the Sales Organization and this mandatory partner function.
    Here are few suggestions.
    1. Since Partner functions are defualted and made mandatory in the Partner Determination Procedure so you have to remove this Mandatory option for PE from the Partner Determination Procedure that is AG if using standard one.
    2. If you are using a single partner function than , Copy and create a New partner procedure and a new account group . Where in one you can default PE as mandatory and in another one you make a optional where it can be choosen manually while creating the customer.
    Follow the path to check for entries :
    SPRO > sales & distribution > Basic Function > Partner Determination > set up partner determination > select for customer master > select the partner procedure you are using AG as standard > then partner function in procedure > here maintian the check as required like, Mandatory or No check for Non Mandatory .
    Thanks
    RB

  • What are the mandatory fields in DTW for opening balances imports?

    Hi All,
    As the title mentions could you please help by listing all the mandatory fields in DTW for importing opening balances ?
    Thank you for your help,
    MB

    Hi Gordon and all,
    I have a look at the SDk help files and almost cried but am i right in thinking it is Account Code, Debit and Credit fields that are the mandatory fields for opening balances?
    These sdk help files are awful by the way...really awful.
    MB

  • Validation for profitability segment in Account document

    Hi Team,
    Currently We are using validation for cost object i.e. either cost center or WBS elements enter  in a  GL account line items and if we are enter both cost object then system will be give Error message . in this validation we have added validation for profitability segment . System will be allow only one at a time enter in Gl accounts (i.e. cost center /WBS elements / profitability segment ). But it is not working for  profitability segment so can you help regarding this.
    Thanks in Advance
    Regards,
    Manas deo

    Hi
    I think you should check
    BSEG-KOSTL <> "" (Blank) AND BSEG-PROJK(WBS) <> ""
    OR
    BSEG-KOSTL<> "" AND BSEG-PAOBJNR <> ""
    OR
    BSEG-PROJK <> "" AND BSEG-PAOBJNR <> ""
    trigger the error msg
    br, Ajay M

  • GL Account Subject for Profitability Segment

    Hi gurus,
    I just want to ask if how will I know if a certain GL account is subject for Profitability Segment (CO-PA).
    Regards
    Andre

    Hi
    I think you should check
    BSEG-KOSTL <> "" (Blank) AND BSEG-PROJK(WBS) <> ""
    OR
    BSEG-KOSTL<> "" AND BSEG-PAOBJNR <> ""
    OR
    BSEG-PROJK <> "" AND BSEG-PAOBJNR <> ""
    trigger the error msg
    br, Ajay M

  • BAPI_INTERNALORDER_CREATE settlement rule for profitability segment

    I am trying to create internal orders using BAPI_INTERNALORDER_CREATE, in the Settlement rules data I want to settle to profitability segment but I can't find away to do this. I can settle to other orders, cost centers and WBS elements but not PSG.
    Are you guys aware of any way I cant do this. How can I derive profitability segment from PNL? is there other functions that will help do this?
    Thank you very much
    Omar

    Yes that field is enabled for settling from settlement profile configuration. The other enabled fields like order, cost centers and profit centers are available.
    I think the BAPI is missing this functionality since the profitability segment has to be derived from other characteristics like PNL.
    Are you guys aware of any functions that do the derivation of the profitability segment given PNL for example?
    In this case where the BAPI is missing some key function what is the best way forward?
    Thanks very much
    Omar

  • Which table is available for profitability segment?

    Hi,
    I have the G/L account, the Profit center and the customer number.
    In which table can I find the profitability segment?
    Thank you.
    Kind regards,
    Linda

    Profitability segment we can find in CE4XXXX
    CE1XXX is for actual line item
    CE2XXX is for plan line item
    CE3XXX is for Summary record by profit segment
    XXXX stands for operating concern
    Assign points if useful

  • User exit for profitability segment in service order settlement rule

    Does anybody know if exit EXIT_SAPLKEAK_001 works for the profitability segment creation during the creation of a settlement rule of a service order?
    The context is the following: the company uses service orders which are settled periodically (it receives revenue from sales order which is posted to the service orders at time of billing, and also costs at time of goods issue). The profitability segment in the settlement rule of the service order needs to be the same as the one from the billing document that posted to the order.
    Can I use EXIT_SAPLKEAK_001 to find the characteristics from the billing document and populate it in the PSG of the settlement rule? If yes, could this be applied to only one specific service order type?
    Thank you.

    Hi
    If your settlement is triggered by a batch or is triggered by a workflow exit EXIT_SAPLKEAK_001 is not run. From release 5.00 on characteristic groups are indeed not considered any more during batch input processes because there were problems before with initial chars of a CO-PA line item resulting from a batch input process that actually shouldn't be initial.
    Refer SAP Note 581739, which put an end to usage of char groups during batch input processes. Also refer SAP Note 142628.
    Regards
    Sanil Bhandari
    Edited by: Sanil K Bhandari on Jun 23, 2011 10:12 AM

  • What are the mandatory fields of BAPI for creating a new purchase order?

    Hi friends,
    I am very new to XI.My Boss has given me task to create a purchase order using BAPI. I want step by step guide to create it.How will i know which fields are mandatory for BAPI_PO_CREATE?

    Hi Shweta,
    However It depends upon the configuration that which fields to be passed.
    But you can check this by running the BAPI in the SAP system by using transaction Se37.
    The most commanly used fields are:
    HEADER :
    DOC_TYPE                       NB
    CO_CODE                        9001
    PURCH_ORG                    9001
    PUR_GROUP                    900
    VENDOR                         100000
    ITEM
    PO_ITEM                        00001
    MATERIAL                      MM10
    STORE_LOC                   01
    MAT_GRP                       01
    SHORT_TEXT                  SERVICE (optional )
    PLANT                            9001
    NET_PRICE                    500
    ITEM_SCHEDULE
    PO_ITEM                        00001
    SERIAL_NO                      0001
    DELIV_DATE                     05.04.2008
    QUANTITY                                  1.000
    You can run the BAPI with some test data... if something is missing the BAPI will ask for it... the Results are displayed in Return Table.
    Regrads,
    Sachin

  • BDC for profitability segment VA02 (sales order)

    Hi all,
    I'm creating a BDC to update the prof.segment from account assignment on a sales item.
    Everything works fine when I run it into the foreground, but when I turn the program in the background, there seems to be an error when opening program 'SAPLKACB' screen '0002'.
    He stops at the screen, and the user has to press on a key to 'push' the program forward.
    Anyone has an idea on how to solve this ?
    This is my code,
    problem lays between the opening of the program, and the start of BDC_OKCODE =COBL_XERGO
    DATA : i_bdcdata            TYPE TABLE OF bdcdata,
             wa_bdcdata TYPE bdcdata,
             wa_pos TYPE posnr_va,
             I_TAB TYPE TABLE OF BDCMSGCOLL,
             wa_tab type BDCMSGCOLL,
             wa_params type CTU_PARAMS.
    refresh i_bdcdata.
    wa_params-dismode = 'A'.
    wa_params-defsize = 'X'.
      CLEAR   wa_bdcdata.
      wa_bdcdata-program  = 'SAPMV45A'.
      wa_bdcdata-dynpro   = '0102'.
      wa_bdcdata-dynbegin = 'X'.
      APPEND wa_bdcdata TO i_bdcdata.
      PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                               'VBAK-VBELN'.
      PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                        '/00'.
      PERFORM add_line TABLES i_bdcdata USING 'VBAK-VBELN'
                                               '0070040656'.
      CLEAR wa_bdcdata.
      wa_bdcdata-program  = 'SAPMV45A'.
      wa_bdcdata-dynpro   = '4001'.
      wa_bdcdata-dynbegin = 'X'.
      APPEND wa_bdcdata TO i_bdcdata.
    *  CLEAR wa_salesorder.
    *loop at the items
      CLEAR wa_pos.
    clear wa_pos.
    *  loop at i_salesorder into wa_salesorder.
    do 2 times.
    *  LOOP AT i_salesorder INTO wa_salesorder.
        wa_pos = wa_pos + 10.
    PERFORM add_line TABLES i_bdcdata USING
    'BDC_OKCODE'
        '=POPO'.
    *    PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
    *    'R45A-MABNR(03)'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPMV45A'.
        wa_bdcdata-dynpro   = '0251'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
        'RV45A-POSNR'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
        '=POSI'.
        PERFORM add_line TABLES i_bdcdata USING 'RV45A-POSNR'
        wa_pos.
    clear wa_bdcdata.
        wa_bdcdata-program  = 'SAPMV45A'.
        wa_bdcdata-dynpro   = '4001'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
        '=ITEM'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
        'RV45A-MABNR(01)'.
        wa_bdcdata-program  = 'SAPMV45A'.
        wa_bdcdata-dynpro   = '4003'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
        '=T\06'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPMV45A'.
        wa_bdcdata-dynpro   = '4003'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
    *perform bdc_dynpro      using 'SAPMV45A' '4003'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                  '/EBACK'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                  'VBAP-KALSM_K'.
        PERFORM add_line TABLES i_bdcdata USING 'DKACB-FMORE'
                                  'X'.
                                  wa_bdcdata-program  = 'SAPLKACB'.
        wa_bdcdata-dynpro   = '0002'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
    PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                  'DKACB-XERGO'.
    PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                  '=COBL_XERGO'.
    PERFORM add_line TABLES i_bdcdata USING 'DKACB-XERGO'
                                  'X'
    *perform bdc_dynpro      using 'SAPLKACB' '0002'.
    *PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
    *                              'COBL-PS_POSID'.
    *    PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
    *                                  '/EBACK'.
    *    PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
    *                              'VBAP-KALSM_K'.
    *    PERFORM add_line TABLES i_bdcdata USING 'DKACB-FMORE'
    *                              'X'.
    *    CLEAR wa_bdcdata.
    *    wa_bdcdata-program  = 'SAPLKACB'.
    *    wa_bdcdata-dynpro   = '0002'.
    *    wa_bdcdata-dynbegin = 'X'.
    *    APPEND wa_bdcdata TO i_bdcdata.
    *    PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
    *                                  '=COBL_XERGO'.
    **PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
    **                              'COBL-AUFNR'.
    *COBL-PS_POSID
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKEAK'.
        wa_bdcdata-dynpro   = '0300'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'RKEAK-FIELD(15)'.
        PERFORM add_line TABLES i_bdcdata USING 'RKEAK-FIELD(15)'
                                      'A1224'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=P+'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKEAK'.
        wa_bdcdata-dynpro   = '0300'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'RKEAK-FIELD(03)'.
        PERFORM add_line TABLES i_bdcdata USING 'RKEAK-FIELD(03)'
                                      'OTH'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=P+'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKEAK'.
        wa_bdcdata-dynpro   = '0300'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'RKEAK-FIELD(07)'.
        PERFORM add_line TABLES i_bdcdata USING 'RKEAK-FIELD(07)'
                                      'BE'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=P+'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKEAK'.
        wa_bdcdata-dynpro   = '0300'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'RKEAK-FIELD(09)'.
        PERFORM add_line TABLES i_bdcdata USING 'RKEAK-FIELD(09)'
                                      'BE'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=P+'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKEAK'.
        wa_bdcdata-dynpro   = '0300'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'RKEAK-FIELD(10)'.
        PERFORM add_line TABLES i_bdcdata USING 'RKEAK-FIELD(10)'
                                      'BE'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=P+'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKEAK'.
        wa_bdcdata-dynpro   = '0300'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'RKEAK-FIELD(11)'.
        PERFORM add_line TABLES i_bdcdata USING 'RKEAK-FIELD(11)'
                                      'REPMC'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=WEIT'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPLKACB'.
        wa_bdcdata-dynpro   = '0002'.
        wa_bdcdata-dynbegin = 'X'.
        APPEND wa_bdcdata TO i_bdcdata.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
                                      'COBL-AUFNR'.
        PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                      '=ENTE'.
        CLEAR wa_bdcdata.
        wa_bdcdata-program  = 'SAPMV45A'.
        wa_bdcdata-dynpro   = '4001'.
        wa_bdcdata-dynbegin = 'X'.
           APPEND wa_bdcdata TO i_bdcdata.
    **PERFORM add_line TABLES i_bdcdata USING 'BDC_CURSOR'
    **                              'RV45A-MABNR(03)'.
    **                                  CLEAR wa_bdcdata.
    **    wa_bdcdata-program  = 'SAPLSPO2'.
    **    wa_bdcdata-dynpro   = '0101'.
    **    wa_bdcdata-dynbegin = 'X'.
    **       APPEND wa_bdcdata TO i_bdcdata.
    **PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
    **                              '=OPT1'.
    *  ENDLOOP.
    enddo.
      PERFORM add_line TABLES i_bdcdata USING 'BDC_OKCODE'
                                '=SICH'.
      CALL TRANSACTION 'VA02'  USING i_bdcdata
                               options from wa_params
                                MESSAGES INTO i_tab.
    break-point.
    FORM add_line TABLES   i_bdcdata STRUCTURE bdcdata
                  USING    bdc
                           value.
      DATA : lw_bdcdata    TYPE bdcdata.
      CLEAR lw_bdcdata.
      lw_bdcdata-fnam     = bdc.
      lw_bdcdata-fval     = value.
      APPEND lw_bdcdata TO i_bdcdata.
    ENDFORM.                    " add_line

    Hello,
    I am having the same issue, How did yuo solve it?
    Thanks,
    Alex

  • Profitability segment optional in recurring entries?

    Hi all!
    I've got a requirement from my customer, the want to use recurring entries (tr code fbd1) where they want the possibility to post to a profitalibilty segment to update COPA. I have checked tr code 07e3 but I cannot find this field possible in any account assignment model. Can anyone please help?
    Thanks in advance!

    Hi,
    If you want to use account assignment model to bring in, the profitability segment while creating the recurring posting template (FBD1), that's is not possible., because of whta you previously indicated, profitability  segment is not in the field selection list. What you may  to do instead,  is to make sure the account(s) you want to post to COPA do have a field status group with profitability segment on (Either as an optional or mandatory field), so while creating the line item in the recurring posting template  the icon "profitability segement" (Right pointing arrow) would be ready for you to access  and the needed fields.
    Hope this helps.
    GG

  • User exit for confirmation of production order for mandatory fields

    While confirming the production order ( CO11 & order type -PP01) , production order should not be saved/confirmed without entering the mandatory field (No. of employees), which is the mandatory field set in the config of "define field selection for confirmation"
    It is allowing if user does't click on the tab (personal/additional data).
    Without entering the mandatory fields in any tab system should not allow user to confirm the order
    How to apply this lock ?
    Also while doing the production confirmation (Co11N) ,user should not have the rights to changes ,adds or delete the component and its quantity OR if user make the changes , suystem should not allow to post the confirmation?How to make this in SAP?
    regards,
    Ramesh Bandi

    Hi,
    You can check the user exit CONFPP05 (Customer Specific Input Checks when Saving) and its function exit  EXIT_SAPLCORF_105 in the transaction code SMOD.
    With this enhancement you can update your own data after saving the confirmation. You cannot change the confirmation itself.
    In this enhancement it is strictly FORBIDDEN to send error messages or other dialogs, otherwise data inconsistencies could occur, for which SAP accepts no liability.
    You can check with your ABAPer's.
    please check & revert back to me.
    Regards,
    Mohan.R

  • DKACB-XERGO Assignment to a profitability segment has no effect for account

    Hi,
    I have a batch input (FB01) in error for this message:
    Assignment to a profitability segment has no effect for account XXXXXXXXXX
    This account is not to opened as cost element...and this is correct.
    If I process batch input in foreground, I notice that field 'Profit. Segment'
    (DKACB-XERGO) is flagged.
    How Can I unflag this field?
    Where 'Profit. Segment' is customized?
    Thanks,
    Marco

    I am wondering what is behind the batch input or what process is used  to do that. For e.g, when I tried entering FB01 transaction with a pure G/L account (it has no cost element) and  clicked on the profitability segment icon, I got the same message what you got.
    So could it be possible that batch input goes through the 'Detail screen for profitability segment' though it may not be required?

  • Mandatory field (profit center) only for F-02

    Hello Friends...
    May I set a mandatory field (profit center) for all accounts (3) and (4) only when I run the transaction F-02??
    Thanks in advanced,
    GLippmann

    Hi,
    You want Profit Center required field in F-02 and for specific series of GL account only.
    This is possible through Validation. (OB28)
    Regards,
    Shayam

Maybe you are looking for