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

Similar Messages

  • 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

  • LSMW-adding Profitability segment in FI document by batch

    Dear all:
    i want to consult that:
    I do the LSMW using the standard batch to post the FI document:
    object :100
    Mehod : 0000
    program name ; RFBIBL00
    Program type: D
    and In my FI document one account is the revenue account and should to assign the PSG ( Profitability Segment)
    and so i  set the related field about the PSG such like RKE_PRCTR ( PSG-profit center)  and so on in the source structure and map them to the related BBSEG's PSG field just like RKE_PRCTR , and i found the read data and convert data, it is ok, but when i excute, it seems the data about the PSG can't upload to the related field, and i'm sure that the field's data is correct, so could you tell me except to map the PSG'S field , which field should i also set? thanks very much

    Hi,
    Can you execute the posting batch in the foreground and revert with the message it returns. In certain screens it should give you a message like:  Screen field XXX-XXXXX does not exist.
    Cheers.

  • 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

  • OB28 - Validation for the G/L Account creation year

    Hello,
    Is there any possible way of doing this validation? Validate G/L Account by the year of creation?
    Ex: No G/L account cant be used if created in 2008!??
    Regard, and thanks in advance,
    Rui Ribeiro

    OB28-Validations can only be maintained for accounting documents(transaction data) not the master data.
    For your requirement go for authorizations by creating new authorization groups/profiles.Please coordinate with the basis(security) team

  • Retrieving Profitability Segment of Accounting Doc

    Hi everyone,
    Is there a function module that you can use to return the profitability segment of an accounting document?  If not, what table can you access to retrieve the profitability segment information, and what parameters do you need?
    Many thanks

    The table that solved my problem was
    CE4xxxx_ACCT
    where xxxx = operating concern

  • IR created for Purchase order without accounting document

    Hi all,
    We have a peculiar situation where an IR (Invoice receipt) document has been created for a purchase order where the corresponding accounting document has not been generated. Can you please let us know how can we create accounting document for this IR.
    We tried to reverse this IR by transaction code MR8M but it is throwing the error message "Reversal not possible, accounting document for the ref. does not exist".
    We understand that there is some standard SAP utility which posts the accounting document and in case there is some configuration also for this, please let us know.
    We would be grateful for any information on resolving this issue.
    Regards,
    Santosh

    Hi,
    Please refer to the below links:-
    http://www.sap-img.com/financial/integration-of-fico-with-other-modules.htm
    http://www.sap-img.com/materials/what-is-the-dataflow-of-mm.htm
    Re: FI-MM(Valuation Class)
    Rgds.

  • 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.

  • Best option for mass G/L Account document (FB50) simulation & creation

    Guyz,
    i'm looking for best option to go for uploading journals after successful simulation througha program....
    i..e, before creating G/L Accounts, i want to simulate and go ahead with real creation....
    do we have any bapi for simulation ?
    Edited by: Kasu on Jan 3, 2008 1:28 PM
    Edited by: Kasu on Jan 3, 2008 1:41 PM

    sorry Thomas.... i meant GL Account document posting (FB50) not creation of G/L Account ....will change the title of the question..... dou know any bapi which has test mode for fb50 ?

  • 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

  • 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

  • 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?

  • How to create a validation for a certain document number range?

    Good Day!
    May I just seek assistance on how to limit a certain document number range from normal posting via F-65?
    The scenario is I would like to restrict, say for example Document Number range 07 from transaction FBV1. How do I create a validation for that? I was thinking what to put up in the Check field in the validation.
    This is how I set up the pre-requsite for the validation rules:
    Pre-requisite:  Transaction Code = FBV1
    Thanks!

    Ok great.. Thanks a lot for the help.If I may just ask one more? =)
    What if the scenario is say creating a validation for a certain GL account group?
    Scenario: User would like to restrict the transaction FBV1 from posting to a GL account group (e.g. G007) ?
    I checked the list of tables and fields in validations, but it seems that the GL account group is not part of the list.
    Any help would be greatly appreciated.

  • Accounting document for Excise Invoice

    Hi,
    Accounting Document generated for Excise Condition types.We do not want to generate Accounting document for Excise Invoice.
    We have marked the Excise Condition types JEXP,JECP,JA1X as Stastical in Pricing procedure & also not assigned the Account Keys for the same.
    How to make other settings for non generation of Accounting document for Excise Invoice.It's a Domestic scenario.
    Please suggets.
    Thanks & Regards,
    Hemant PAtil

    Hi,
    Instead of creating the Excise Group i have created the Sub Trasaction type (DS) ETT Type DLFC.
    In SPRO Specified the Excise Account per Excise Transaction DLFC & DS.
    Also Specified G/L Accounts per Excise Transactions.
    Excise Grp (P2),ETT (DLFC),Company Code (MU51),Chart of Accts(XXX),all the G/L Accounts kept BLANK.
    While creating the Excise Invoice thor.J1IIN,if i put Sub Transaction type DS then the system gives the following error.
    Excise modvat accounts not defined for DLFC transaction and  excise group
    Message no. 8I402
    Please suggests.
    Thanks & Regards,
    Hemant Patil

Maybe you are looking for