Company code data not maintained ERROR

I have defined company code, plant, str loc, purchase org, and i have assigned all those things. i have also assigned to controlling area.   in ec01  it is showing the structure but while creating the Material master for that particular plant it is showing the msg Company code data not maintained.

Hi Praveen,
It seems from your explanation that you havent maintained company code for Materials management,
Got to transaction OMSY maintain your company code for present fiscal year and period.
I hope this will will solve your Issue.
With Regards,
Vijaykumar Panchagattimath

Similar Messages

  • Company code does not exist error while sending idoc

    Hi Expert
    I am trying to send idoc from one client(800) to another client(810).I have faced error Company code does not exist, searched scn ,Got solution if company code does not exist in reciever system(810 client) ,it will show this error  .Then i have tried to give specific company code which is exist in 810 client also .But same issue is coming . So what exactly the issue can any one say .
    More Info:FI(Finance) header items and line items are sending .
    Thanks & Regards

    Hi,
    Your company code not activated for material management. Few pre-requisites to create material and one is to activate company code for material management
    Please activate in T.code: OMSY,
    [For example: For Fiscal year variant K4]
    In OMSY steps, u have to enteru2026u2026u2026..
    Company Code (enter your company code name 2001)u2026u2026u2026u2026u2026.
    Company Name..
    Fiscal Year of Current Period 2009
    Current period (posting period) 03( )
    Fiscal year of previous period 2008( will come automatic)
    Month of previous period 02( will come automatic)
    Fiscal year of last period of previous year 2008
    Last month of previous year 12
    Allow Posting to Previous Period (Back posting)
    Disallow back posting after a change of period
    Now create material with T.code; MM01
    Regards,
    Biju K

  • Help - Error in PR BAPI :  Purchasing across company codes is not allowed..

    I have written a program to create Purchase Requisition.I am using two BAPIs.In the file i specify the old PR No, New Plant,Purch Group and Purch Org.It is actually a program to create a new PR in a new plant which is a copy of an Old PR in older plant.
    Program is below:
    I am getting the error Purchasing across company codes is not allowed..
    Please Help
    *& Report  ZMMB_BDC_ME51N_WO
    REPORT  ZMMB_BDC_ME51N_WO.
    INITIALIZATION.
    D A T A   D E C L A R A T I O N                                     *
      TYPES: BEGIN OF TY_TABDATA,
              BANFN TYPE EBAN-BANFN, " Purchase Requistion No
              WERKS TYPE MEREQ3211GRID-WERKS, "Plant
              EKGRP TYPE MEREQ3211GRID-EKGRP, "Purchasing Group
              EKORG TYPE MEREQ3211GRID-EKORG, "Purchasing Organization
             END OF TY_TABDATA.
      TYPES: BEGIN OF TY_CHECK,
                BANFN TYPE EBAN-BANFN, " Purchase Requistion No
                BNFPO TYPE EBAN-BNFPO, " Purchase Requistion Item No
                EBAKZ TYPE EBAN-EBAKZ, " PR Closed
             END OF TY_CHECK.
    Declaration of the Internal Table & Work Area.
      DATA:
             IT_TABDATA         TYPE  STANDARD  TABLE  OF   TY_TABDATA, " Internal Table for file
             WA_TABDATA         TYPE                       TY_TABDATA.
      DATA: IT_ITEM TYPE STANDARD TABLE OF BAPIEBAN ,
            WA_ITEM LIKE LINE OF IT_ITEM,
            IT_ITEM1 TYPE STANDARD TABLE OF BAPIEBANC,
            WA_ITEM1 LIKE LINE OF IT_ITEM1,
            IT_ACCOUNT TYPE STANDARD TABLE OF BAPIEBKN,
            WA_ACCOUNT LIKE LINE OF IT_ACCOUNT,
            IT_PRITEMTEXT TYPE STANDARD TABLE OF BAPIEBANTX,
            WA_PRITEMTEXT LIKE LINE OF IT_PRITEMTEXT,
            IT_SERVICES TYPE STANDARD TABLE OF BAPIESLL ,
            WA_SERVICES LIKE LINE OF IT_SERVICES,
            IT_SERVICES1 TYPE STANDARD TABLE OF BAPIESLLC ,
            WA_SERVICES1 LIKE LINE OF IT_SERVICES1,
            IT_SERVICETEXT TYPE STANDARD TABLE OF BAPIESLLTX,
            WA_SERVICETEXT LIKE LINE OF IT_SERVICETEXT,
            IT_CHECK TYPE STANDARD TABLE OF TY_CHECK,
            WA_CHECK LIKE LINE OF IT_CHECK.
       Global data Declaration
      DATA:   GV_YEAR(4)         TYPE C,
              GV_MNTH(2)         TYPE C,
              GV_DATE(2)         TYPE C,
              GV_DATUM(8)       TYPE C,
              GV_ANS TYPE C,
              W_FILENAME      TYPE  STRING.
    Declaration of the Internal Table with Header Line comprising of the uploaded data.
      DATA:  BEGIN  OF  IT_FILE_UPLOAD  OCCURS  0.
      INCLUDE  STRUCTURE  ALSMEX_TABLINE.  "  Rows for Table with Excel Data
      DATA:  END  OF  IT_FILE_UPLOAD.
    Batch Input Data for a single Transaction.
    Message of Call Transaction.
      DATA:  BDCDATA  LIKE  BDCDATA     OCCURS  0  WITH  HEADER  LINE,
             MSGTAB   LIKE  BDCMSGCOLL  OCCURS  0  WITH  HEADER  LINE.
    S E L E C T I O N - S C R E E N                                     *
      SELECTION-SCREEN:  BEGIN  OF  BLOCK  B1  WITH  FRAME TITLE TEXT-001,
                             BEGIN  OF  BLOCK  B2  WITH  FRAME TITLE TEXT-004.
      PARAMETERS: P_FNAME  LIKE  RLGRAP-FILENAME  OBLIGATORY.
      SELECTION-SCREEN:      END  OF  BLOCK  B2,
                         END  OF  BLOCK  B1.
    E V E N T : AT    S E L E C T I O N - S C R E E N                   *
    AT  SELECTION-SCREEN  ON  VALUE-REQUEST  FOR  P_FNAME.
      CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
        EXPORTING
          STATIC    = 'X'
        CHANGING
          FILE_NAME = P_FNAME.
    E V E N T : S T A R T - O F - S E L E C T I O N                     *
    START-OF-SELECTION.
    Upload Excel file into Internal Table.
      PERFORM  UPLOAD_EXCEL_FILE.
      IF  NOT  IT_FILE_UPLOAD  IS  INITIAL.
      Confirm whether you want to proceed with the Upload.
        PERFORM  CONFIRM_UPLOAD.
        IF  GV_ANS  EQ  '1'.
      Organize the uploaded data into another Internal Table.
          PERFORM  ORGANIZE_UPLOADED_DATA.
          PERFORM BAPI_CALL.
        ENDIF.
      ELSE.
        LEAVE PROGRAM.
      ENDIF.
    *&      Form  UPLOAD_EXCEL_FILE
          text
    -->  p1        text
    <--  p2        text
    FORM UPLOAD_EXCEL_FILE .
      CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
        EXPORTING
          FILENAME                = P_FNAME
          I_BEGIN_COL             = 1
          I_BEGIN_ROW             = 4
          I_END_COL               = 4
          I_END_ROW               = 9999
        TABLES
          INTERN                  = IT_FILE_UPLOAD
        EXCEPTIONS
          INCONSISTENT_PARAMETERS = 1
          UPLOAD_OLE              = 2
          OTHERS                  = 3.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " UPLOAD_EXCEL_FILE
    *&      Form  CONFIRM_UPLOAD
          text
    -->  p1        text
    <--  p2        text
    FORM CONFIRM_UPLOAD .
      CALL FUNCTION 'POPUP_TO_CONFIRM'
        EXPORTING
          TITLEBAR       = TEXT-002
          TEXT_QUESTION  = TEXT-003
        IMPORTING
          ANSWER         = GV_ANS
        EXCEPTIONS
          TEXT_NOT_FOUND = 1
          OTHERS         = 2.
    ENDFORM.                    " CONFIRM_UPLOAD
    *&      Form  ORGANIZE_UPLOADED_DATA
          text
    -->  p1        text
    <--  p2        text
    FORM ORGANIZE_UPLOADED_DATA .
      DATA : GV_TOTROW TYPE I, "No of records
              GV_ROW TYPE I,
              LC_CNT(3) TYPE N.
      GV_TOTROW = 1.
      SORT  IT_FILE_UPLOAD  BY  ROW
                              COL.
      LOOP AT IT_FILE_UPLOAD.
        GV_TOTROW = IT_FILE_UPLOAD-ROW.
      ENDLOOP.
      GV_ROW = 1.
      WHILE GV_ROW <= GV_TOTROW.
        LOOP  AT  IT_FILE_UPLOAD WHERE ROW = GV_ROW.
          CASE  IT_FILE_UPLOAD-COL.
            WHEN '0001'.
              WA_TABDATA-BANFN = IT_FILE_UPLOAD-VALUE.
            WHEN '0002'.
              WA_TABDATA-WERKS = IT_FILE_UPLOAD-VALUE.
            WHEN '0003'.
              WA_TABDATA-EKGRP = IT_FILE_UPLOAD-VALUE.
            WHEN '0004'.
              WA_TABDATA-EKORG = IT_FILE_UPLOAD-VALUE.
          ENDCASE.
        ENDLOOP.
        GV_ROW = GV_ROW + 1.
        APPEND WA_TABDATA TO   IT_TABDATA .
        CLEAR :WA_TABDATA.
      ENDWHILE.
    ENDFORM.                    " ORGANIZE_UPLOADED_DATA
    *&      Form  BAPI_CALL
          text
    -->  p1        text
    <--  p2        text
    FORM BAPI_CALL .
      DATA:ITM_NO(4) TYPE N,LV_PERCENTAGE(3) TYPE N,
           LV_MSG(60),
           IT_RETURN TYPE STANDARD TABLE OF BAPIRETURN,
           WA_RETURN LIKE LINE OF IT_RETURN.
      DATA: BEGIN OF WA_RETURN1,
            BANFN TYPE EBAN-BANFN.
      INCLUDE  TYPE BAPIRETURN.
      DATA END OF WA_RETURN1.
      DATA:IT_RETURN1 LIKE STANDARD TABLE OF WA_RETURN1.
      DESCRIBE TABLE IT_TABDATA LINES ITM_NO.
      LOOP AT IT_TABDATA INTO WA_TABDATA.
        CALL FUNCTION 'BAPI_REQUISITION_GETDETAIL'
          EXPORTING
            NUMBER                               = WA_TABDATA-BANFN
           ACCOUNT_ASSIGNMENT                   = 'X'
           ITEM_TEXTS                           = 'X'
           SERVICES                             = 'X'
           SERVICE_TEXTS                        = 'X'
          TABLES
            REQUISITION_ITEMS                    = IT_ITEM
           REQUISITION_ACCOUNT_ASSIGNMENT       = IT_ACCOUNT
           REQUISITION_TEXT                     = IT_PRITEMTEXT
      REQUISITION_LIMITS                   =
      REQUISITION_CONTRACT_LIMITS          =
       REQUISITION_SERVICES                 = IT_SERVICES
       REQUISITION_SERVICES_TEXTS           = IT_SERVICETEXT
      REQUISITION_SRV_ACCASS_VALUES        =
      RETURN                               =
        COMPUTE LV_PERCENTAGE = ( ITM_NO / SY-TABIX ) * 100.
        CONCATENATE 'PROCESSING PURCHASING REQUISITION FOR OLD PR NUMBER ' WA_TABDATA-BANFN INTO LV_MSG.
        CALL FUNCTION 'RM_SAPGUI_PROGRESS_INDICATOR'
          EXPORTING
            PERCENTAGE = LV_PERCENTAGE
            TEXT       = LV_MSG.
        CLEAR:LV_PERCENTAGE ,LV_MSG.
        IF IT_TABDATA[] IS NOT INITIAL.
          SELECT BANFN BNFPO EBAKZ FROM EBAN INTO TABLE IT_CHECK FOR ALL ENTRIES IN IT_TABDATA
              WHERE BANFN = IT_TABDATA-BANFN AND EBAKZ = 'X'.
        ENDIF.
        LOOP AT IT_CHECK INTO WA_CHECK.
          LOOP AT IT_ITEM INTO WA_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
            DELETE IT_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
          ENDLOOP.
          LOOP AT IT_ACCOUNT INTO WA_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
            DELETE IT_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
          ENDLOOP.
        ENDLOOP.
        LOOP AT IT_ITEM INTO WA_ITEM.
          WA_ITEM-PLANT = WA_TABDATA-WERKS.
          WA_ITEM-PUR_GROUP = WA_TABDATA-EKGRP.
          WA_ITEM-PURCH_ORG = WA_TABDATA-EKORG.
          MODIFY IT_ITEM FROM WA_ITEM TRANSPORTING PLANT PUR_GROUP PURCH_ORG.
          MOVE-CORRESPONDING WA_ITEM TO WA_ITEM1.
          WA_ITEM1-PREQ_NO = ''.
          WA_ITEM1-STORE_LOC = ''.
          APPEND WA_ITEM1 TO IT_ITEM1.
          CLEAR WA_ITEM1.
        ENDLOOP.
        LOOP AT IT_ACCOUNT INTO WA_ACCOUNT.
          WA_ACCOUNT-PREQ_NO = ''.
          MODIFY IT_ACCOUNT FROM WA_ACCOUNT TRANSPORTING PREQ_NO.
        ENDLOOP.
        LOOP AT IT_SERVICES INTO WA_SERVICES.
          MOVE-CORRESPONDING WA_SERVICES TO WA_SERVICES1.
          APPEND WA_SERVICES1 TO IT_SERVICES1.
          CLEAR WA_SERVICES1.
        ENDLOOP.
        CALL FUNCTION 'BAPI_REQUISITION_CREATE'
       EXPORTING
         SKIP_ITEMS_WITH_ERROR                =
         AUTOMATIC_SOURCE                     = 'X'
       IMPORTING
         NUMBER                               =
          TABLES
            REQUISITION_ITEMS                    = IT_ITEM1
           REQUISITION_ACCOUNT_ASSIGNMENT       = IT_ACCOUNT
           REQUISITION_ITEM_TEXT                = IT_PRITEMTEXT
         REQUISITION_LIMITS                   =
         REQUISITION_CONTRACT_LIMITS          =
          REQUISITION_SERVICES                 = IT_SERVICES1
         REQUISITION_SRV_ACCASS_VALUES        =
           RETURN                               = IT_RETURN
          REQUISITION_SERVICES_TEXT            = IT_SERVICETEXT
         REQUISITION_ADDRDELIVERY             =
         EXTENSIONIN                          =
        READ TABLE IT_RETURN INTO WA_RETURN INDEX 1.
        IF WA_RETURN-TYPE = 'E'.
          CLEAR WA_RETURN.
          LOOP AT IT_RETURN INTO WA_RETURN WHERE TYPE EQ 'E'.
            WA_RETURN1-BANFN = WA_TABDATA-BANFN.
            MOVE-CORRESPONDING WA_RETURN TO  WA_RETURN1.
            APPEND WA_RETURN1 TO IT_RETURN1.
            CLEAR WA_RETURN1.
          ENDLOOP.
        ELSE.
          WA_RETURN1-BANFN = WA_TABDATA-BANFN.
          MOVE-CORRESPONDING WA_RETURN TO  WA_RETURN1.
          APPEND WA_RETURN1 TO IT_RETURN1.
          CLEAR WA_RETURN1.
        ENDIF.
        IF SY-SUBRC <> 0.
        ENDIF.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
             WAIT          =
           IMPORTING
             RETURN        =
        REFRESH: IT_RETURN[],IT_ITEM[],IT_ACCOUNT[],IT_PRITEMTEXT[],IT_ITEM1[],IT_SERVICES[],IT_SERVICES1[],
                 IT_SERVICETEXT[].
      ENDLOOP.
      WRITE :10 'OLD PR NUMBER' COLOR COL_KEY, 25 'MESSAGE' COLOR COL_KEY.
      LOOP AT IT_RETURN1 INTO WA_RETURN1.
        WRITE:/10 WA_RETURN1-BANFN,25 WA_RETURN1-MESSAGE.
      ENDLOOP.
      CLEAR:IT_TABDATA[],WA_TABDATA.
    ENDFORM   .                 "BAPI_CALL

    Solved on Own

  • Delivery should not create with out company code data

    Hi all,
              We have created a customer master without company code data with T code VD01 and subsequently created sales order and delivery with PGI and invoice also saved but no accounting document is getting generated. But we want to stop at delivery only; system should not allow creating delivery. Please do the needful
    Thanks in advance
    Regards,
    Nagesh

    hi nagesh,.
    from standard SAP it might not be possible.
    but check this work around:
    after creating the COMPANY CODE DATA by the marketing people only you please go ahead and create a delivery till that time the sales order will be in open status.
    if you want to stop it through the SAP system:
    then you need to contact TECHNICAL PERSON on the same:
    MV45AFZZ : USEREXIT_SAVE_DOCUMENT_PREPARE for checking while creating a delivery if not created then to throw an ERROR message - this is the only probability to check
    but he may not be having solution for your query.
    except the work around.
    please check and confirm
    balajia

  • Error in F110 posting telling that company code does not appear in proposal

    Hi Everyone,
    During the aotumatic payment run via F110, after creating the proposals when i am trying to display the proposal, it is giving an error message that " Company Code XY12 / XY12 does not appearin proposal 08.07.2011 AB00; correct "
    But I already set company code XY12 , in the company code in the parameter tab. I ahve also set there payment methods and next payment date. Please help.

    Hi Dear,
    Chk these links
    http://sap-f2.blogspot.com/2009/06/fz003-company-codes-do-not-appear-in.html
    Company codes 0001/0001 do not appear in proposal 20.11.2009 A#04; correct
    http://www.sapfans.com/forums/viewtopic.php?f=10&t=188134

  • Country IN does not store a hard currency while editing company code data

    hi, i am new to sap. i defined company n company code (copying from std) and edited company code data, while trying to save that getting error "Country IN does not store a hard currency". please guide me what have to do to over come this. thanks

    GOTO   OY01
    select your country code ( here IN )
    select IN, GOTO details (ctrl shiftf2)
    change language to EN & hard currency to INR, save it
    Regards
    sidhartha

  • BDC error CO assingnment object  belong to company code A800 not A900

    Hi,
    I am getting  BDC error 'CO assingnment object  belong to company code A800 not A900'.
    Please any one suggest the reason for this.
    Thakns in advance.

    Hi,
    you are processing a BDC-session for company code A900 with a CO-account assignment for comp. code A800 and your system does not allow cross-company code postings. Check the co-object and correct it.
    Best regards, Christian

  • Company code could not be determined for IDoc #.......

    I was trying to generate an IDoc manually by using the tcode WE19. I have manually keyed the data in to the respective segments for the basic type PEXR2002 and message type REMADV. After this while processing, the IDoc is getting generated, but not posted OK. I am getting the following two error messages 51 stating:
    'Company code could not be determined for the IDoc #....'
    'Customer/vendor could not be determined for the IDoc #.'
    Can any one give some inputs on this issue?
    Shaji
    Message was edited by: Shaji Thomas

    Hi Shaji,
    You may look at the OSS note 316811.
    Thanks
    Vinod

  • How to add company code data to BP in SAP CRM

    Hi All
    I have a problem replicating BP from CRM to R3,the error coming is "Fill in the required entry fields".
    While debugging the error i came to know that Company Code data is not given from CRM side which is mandatory in R3.
    Actually the Company code data is kept mandatory at ABAP level due to the Client requirement.
    Now how can i add the company code data to BP so that this errors is resolved.As far as my knowledge goes there is no provisions for company code data in CRM ,now even if we keep this company code data optional in R3 ,this error is coming.
    Please suggest the way out.
    Any help will be highly appreciated.
    Regards
    Ashish

    Hi there
    Thanks for the reply,yeah i understand that there is no company code concept in CRM system.
    so,we mean by Middleware exit is the user exit at R3 side,that i understand too.
    But here scenario is different in the case that customer is not getting replicated due to the company code being kept mandatory at ABAP level in R3.
    Actually client requires the company code data to be mandatory in R3 so that customer id does not get generated in R3 without giving the company code info.
    Now due to the mandatory check on company code at ABAP level ,what happening is that we are not able to replicate the BP info to R3 because if that check was not there we would have at least pass on the BP data except the company code  and company code info would have been given in R3 itself.
    So,i believe the way out is to remove that check and place a user exit in R3 so that at least CRM data is replicated and company code will come automatically.
    Hope this will help me,if you have any better suggestion then please provide the same.
    Regards
    Ashish

  • "Company code  is not permitted as the paying company code while FRFT

    Hi Experts,
    I am trying to post cross company fund transfers via FRFT -> F111. In my scenario, CC1 is sending amount to CC2 via a virtual payment method. I have done basic company code set up and also customizations in FBZP for payment method and F8BJ/F8BF for incoming/outgoing transactions. I have also done OBYA setting for cross company clearing account
    During FRFT payment request i get this error: "Company code CC1 is not permitted as the paying company code".
    Did you ever experience this? If so, how can i fix this?
    Thanks in advance.

    Dear subumax
    1.Please check once again in both company codes for FBZP. were you maintained in All Company codes in FBZP - Select your company code and check- were you maintained Paying company code.
    2.Pleasecheck in under Paying Company codes - were you maintained the paying company code CC1 or not
    3Please check in under Payment methods in comapny code were you maintained your paying company code code CC1 details or not 
    Regards
    Shankar

  • Control message "Purchase across Company codes is not allowed"

    Hello Gurus
    We are running SRM5.0 ECS using EP. If we attempt to create a SC that falls foul of the above validation, we get a message but only as a warning. Naturally if a warning, users will ignore and continue the purchasing process up to the point that the PO is created. However, when the PO is transferred to the ECC, we get the "Error in Process" status for the same message, but ECC validation routines have this set to an error and not a warning.  Evidently there is a discrepancy with severity between SRM and ECC. We want to ensure that SRM matches up to ECC so it is an error in SRM and not a warning.
    Searching the web, I see that the message id is KI-113. Can't be sure this is correct as the portal we use does not display the msg id. I've checked the message control config in SRM, and see nothing for the message. Further investigation reveals that in order to control messages through the config, you can only maintain those that are listed in BBPV_PDMSG. After searching for id or text, I still cannot see how I can escalate ths message to an error.
    Any ideas?
    Thanks
    Ian

    Hi peggy
    This message comes from your r/3 backend system. go to se91 KI - message no. 113 in sap r/3.
    it is not srm message.
    Error : Purchasing across company codes is not allowed
    BR
    Muthu
    Edited by: Muthuraman Govindasamy on Oct 13, 2008 10:17 AM

  • Msg K1100 'The CO account assignment object belongs to company code X,not Y

    Hi,
    Unable to create an accounting document for a Return order.
    Message K1100 - Error:The CO account assignment object belongs to company code X,not Y
    Company Code : X
    Sales Org: X
    Plant: P
    Billing Date : IG ( Internal Credit Memo)
    The above details are from the item level- Account Assignment tab-Profitabliity Segment.
    Pl. let us know from which table these fields are picked.
    Regards
    Biju
    Edited by: Biju Mercy on Jan 7, 2010 12:58 PM

    I believe the error message number is ki100 and not  k1100  as indicated by you in which case, refer any of the following notes:-
    a)  140503
    b)  643700
    c)  420778
    d)  352261
    e)  141224
    thanks
    G. Lakshmipathi

  • The CO account assignment object belongs to company code 2100, not 1100

    Hi All,
    My system has all different company codes assigned to one cotrolling area as a result one can change org unit and position cost center from one company code to another.
    I recently changed same position's cost center from co code 2000 to cost center in new  co code 1100 and created new personnel area to be linked to new Co code 1100. OM module doesn't moan however when I try and capture org-reassignment action to default same employee postion with new related cost center from new company code 1100 get the follwing error.
    'The CO account assignment object belongs to company code 2100, not 1100'.
    I see in IT0001 system defaults new personnel area linked to Co code 1100 however it still defaults old cost center linked to Co code 2000 instead of new cost center linked to Co code1100. How can I make the system default  new cost center?
    NB relationship for new cost center  from Co code 1100 to postion has been changed effective 01.04.2012 . The same date is used for or-reassignment action.

    Hi I had same problem can you explain me little bit more that how you will resolve this

  • No company code data available in XD01

    Hi All,
    I'm facing a issue in XD01 transaction code.
    In my current client process of creation of customer is first Master data team is responsible for creation of  General data segment of the customer once general segment is created it comes to SD user who is responsible for creation of company code and sale are segment. SD user donu2019t have authorization to create general segment u2013once general segment is created by MDM then only system will allow to create other segment by SD user.
    In production system when SD user use XD01 to create company  and sale area segment that user is not able to see Company code segment and user is calming that  earlier they are able to see company code segment.  I checked with S&A team as per them there is no changes in roles and authorization for that particular user since beginning.
    So to test what is the problem I requested S&A to create a test id in quality system with same role and authorization what SD user having in production system. I asked MDM to create a customer but when I (I mean test user created in Quality system )try to use XD01 to create other segment then system through a error saying u201CCustomer 830587 has already been created company code NLYQ sales area NLYQ SV PHu201D. Mean system is not allowing me to enter inside through XD01 because customer is already created but user is able to enter through XD01      in production. How it is possible Iu2019m using same roles and authorization what User having in production system.  if in production user is able to enter then with help of test id it should also allow to enter inside XD01 in quality also .
    I checked SU53 also even I asked S&A to activate tracing on Test id in quality so that we will find missing authorization during my testing in su53 and log we found nothing.
    So just wanted to know how it is possible or how I can get company code data in production system for that particular user.
    Thanks
    Prakash Sharma

    Dear Madhu ,
    Yes user is giving company code in selection parameter and there is BDC for creation of Customer. MDM is using that BDC for creation of general segment of customer
    Regards
    Prakash Sharma
    Edited by: Prakash Sharma on Jun 20, 2011 2:23 PM

  • Saved Document Number needed after saving the customer  company code data

    I created a customer than I saved the company code data and forgot to note the number the saved document number. Next time I went to the same customer again and I wanted to find out the saved document number for the same customer but did not know where to look for. Can you tell me what I should do?
    Thanks

    Hi,
    For any customer there will be general data,Company code data and sales area data.
    Even though you maintain the general data or company code data  only one numebr will be generated.
    If you want to maintain some other data as comapny code data and sales area data we will goto XD02 and enter the company code,sales area nd customer number in the initial screen and we will maintain that data.
    I think you are thinking that different number will be created for different data which is wrong.
    So enter the same number and company code in XD03 and view your data.
    Regards,
    Krishna.

Maybe you are looking for