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

Similar Messages

  • 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

  • The CO account assignment object belongs to company code PN10, not BN10

    Hi All, Iu2019m getting the error u201CThe CO account assignment object belongs to company code PN10, not BN10" when trying to make a payment on an invoice that was created in company code BN10.
    The error came about because, there was an exchange rate difference between the invoice value and the corresponding payment value (document currency is USD and the transaction I'm using to make payment is F-58).
    Therefore when i try to make the payment, the SAP system detects the exchange rate difference and attempts to post it to the exchange rate difference account (421020050). In OKB9, the default cost center specified for G/L account (421020050) in BN10 is (B999010). Therefore when the payment is been done, the system posts the exchange rate difference to G/L account (421020050) and assigns the cost center (B999010).
    However, upon trying to save the document, the system shows the message "Correct the marked line items" (the marked line item here is the exchange rate line item). Therefore, I double click the line item to drill down on it and see that everything seems fine. I then click the save button, on clicking it, the system shows the error "The CO account assignment object belongs to company code PN10, not BN10u201D.
    When i double click the error to read a more comprehensive explanation of the error, its content are as displayed below:
    The CO account assignment object belongs to company code PN10, not BN10
    Message no. KI100
    Diagnosis
    You want to make a posting in company code BN10.
    At the same time, a CO account assignment object was specified that is assigned to company code PN10.
    This is account assignment object with object type CTR, and object key NIG1/A999010.
    System Response
    Company code validation is active for company code BN10:
    All account assignment objects in one posting row must be assigned to the same company code.
    Procedure
    You can
    u2022     Make an assignment to company code PN10.
    u2022     Enter an account assignment object assigned to company code BN10.
    u2022     Change the assignment of object NIG1/A999010 to company code PN10. In this case, you should note the document and edit it further after changing the assignment.
    If the posting is to a balance sheet account (category 90), you may also decide whether to allow CO account assignment objects from other company codes. If this is the case, deactivate the error message with the IMG step Change message control (message ID "KI", message number 100).
    You can set the following message types:
    "-"   Message is not sent
    "W"   Message is sent as a warning message
    "E"   Message is sent as an error message
    Posting to cost elements of another category always results in the message appearing as an error message, whether it has been deactivated or not.
    Execute "Change message control"
    (NOTE: All cost centers that starts with u201CAu201D belong to company code PN10 and those that starts with u201CBu201D belong to company code BN10)
    Kindly help with the resolution of this issue. Any resolution ideas would be greatly appreciated.
    Moderator: Please, search SDN

    Check the following OSS notes
    1)  Note 141224 - Error message KI100 for cross company
    2)  Note 202765 - KI100 during release of intercompany billing
    thanks
    G. Lakshmipathi

  • The CO account assignment object belongs to company code 4007, not 4440

    Hi,
    I am Loading Employee data (PA0001) and getting the following error.
    The CO account assignment object belongs to company code 4007, not 4440
    Can anybody clarify me.
    Thanks,
    Aparna

    Hi Aparna,
    Default Cost Assignments arent properly configured. Check TCODE OKB9 and get the assignments rectified with the help of FI Consultant.
    For more understanding, follow the link
    [Error in PA 40  The CO account assignment object belongs to company code XX]
    Hope this helps !!!!
    Kumarpal Jain.

  • CO account assignment object belongs to company code SE01, not DK01

    Hi SAP Gurus,
    I am posting one inter company billing document.  Customer is from Denmark and material is supplied from Sweden Co Code.  Our requirement is to update the cost center field for the intercompany code document SE01.  I have done following customizing in order to update Cost center field for inter company billing document for CoCd SE01.
    1. Create order reason - OVAU
    2. Maintain default cost center for order reason in tranx OVF3
    I am encountering following error while trying to release billing doucment for account.
    Diagnosis
        You want to make a posting in company code DK01.
        At the same time, a CO account assignment object was
        specified that is assigned to company code SE01.
        This is account assignment object with  object type CTR,
        and object key CMAX/SE9001.
    System Response
        Company code validation is active for company code DK01:
        All account assignment objects in one posting row must be
        assigned to the same company code.
    Procedure
        You can
        o   Make an assignment to company code SE01.
        o   Enter an account assignment object assigned to company
            code DK01.
        o   Change the assignment of object CMAX/SE9001 to company
            code SE01. In this case, you should note the document
            and edit it further after changing the assignment.
        If the posting is to a balance sheet account (category 90),
        you may also decide whether to allow CO account assignment
        objects from other company codes. If this is the case,
        deactivate the error message with the IMG step Change
        message control (message ID "KI", message number 100).
        You can set the following message types:
            "-"   Message is not sent
            "W"   Message is sent as a warning message
            "E"   Message is sent as an error message
        Posting to cost elements of another category always results
        in the message appearing as an error message, whether it
        has been deactivated or not.
        Execute "Change message control"
    Please let me know if you face such a issue in past.
    Regards,
    SATVIR SINGH
    Moderator: I trust, SAP explanation is quite sufficient

    Hi Satvir
    You have switched on Comp Code validation in OKKP... which means you can not post to CO objects of another company code...
    Eg: If billing is from comp code A, the co object has to be from same comp code.... Try to use OKB9 and specify a default CO object for the GL account involved in the posting or specify a default Cost center in OVF3 pertainig to the other comp code
    Regards
    Ajay M

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

    Dear consultants,
    I am SAP - HR consultant.
    I have 4 company codes, under one controlling area & payroll area. I executed live Payroll & tried to run posting payroll results. System displayed folloewing error "You want to make a posting in company code 1100. At the same time, a CO account assignment object was specified that is assigned to company code 1000. This is account assignment object with object type CTR, and object key 1000/1010101400. "
    I have created similar accounts 1110101400, 1210101400 & 1310101400 for company codes 1100, 1200 & 1300.
    May I know what could be the reason?
    Regards,
    Bindumadhav

    "this is account assignment object with object type CTR, and object key 1000/1010101400" means; somethings is missing for cost center 1010101400 under the company code 1000. system tries to post and entry for company code 1100 to the cost center 1010101400 which falls under a different company code (1000).
    so it is not realted with GL accounts i believe
    you can go to KS02 and check the company code for the CCenter 1010101400 and change it to 1100.
    or you may change the cost center assigned to employer master and give a new ccenter which is under the company code 1100.
    but if i were you, before making any changes i would consult the a CO consultants first for this issue.

  • The CO account assignment object belongs to company code AA01, not AB01

    Dear Experts:
    I am doing Asset Transactions. I've created Order and Asset but when I'm going to create Purchase Requisition in T-code: ME51N, I'm facing below error but I'm fully in dark why this is happening because earlier we did all these entries correctly without any problem but suddenly I'm facing this issue.
    Would you please suggest me how can I overcome this situation.
    Thanks in advance and your suggestion is highly appreciated.
    Best Regards.
    Ripon Kumar Paul

    Dear Ravi and Ajay:
    Internal Order No. 600403 has been created in Company Code AB01. Please find below the screen shots of Internal Order and Purchase Requisition for your reference. Would you please check and suggest how we can provide correct CO Object? I'm really in dark and don't know much about controlling.
    Thanks and best Regards.
    Ripon Kumar Paul

  • Error In Transfer The CO account assignment object belongs to company code

    Dear All,
    When i am trying to transfer a employee from a personnel area to another personnel area, i am getting the following error.
    The CO account assignment object belongs to company code 2000, not 2007
    These personnel areas belong to two different company codes.
    Pls suggest.
    Kind Regards
    Nag

    Hi,
    Please check with the FICO consultant you have to give new CO assignemnt when you transfer  EMPLOYEE to other companycode. i hope so
    Vibin

  • Cost center belongs to company code 1000, not 2000

    Hi,
       When i am entering cost center in sales order, I am getting  an error "Cost center belongs to company code 1000, not 2000"
    Does anyone know which transaction i can use to extend this cost center to a different company code?

    I think you are creating sales rder for plant 1000. While the cost center you are providing is attched to plant 2000. Either you can change the cost center for plant 1000 or you can change the customiztion so that cost center is attached to plant 1000.

  • 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

  • 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

  • IDocStatus:Error in ALE service Cross-system company code does not exist

    HI All,
    I am sending CREMAS04 IDOC from XI to one R/3 system,and in R/3 a vendor should get created in master table.
    My IDOC is getting posted successfully but in R/3 system I am getting error that
    IDoc: 0000000000705816 Status: Error in ALE service
    T100 Text: Cross-system company code XXX does not exist
    I have created partner profiles in receiver system and in partner profiles I have set the process code as CRE1.
    Please help me to resolve this problem.

    Hi Shweta
    Have you checked with the data i.e. company code .
    May the company code which you are passing is not there in ur receiver system.
    Just check it out.
    Regards
    -Mitesh

  • "Account Assignment objects have differing company codes"

    Hi,
    We have parked the document through T.Code : MIR7 & now we want to post the same using the correct GL A/c.
    When we try to post the document we are getting error like "Account Assignment Objects have differing Company Codes"
    Can you please help me
    Thanks
    Ravi kumar

    Please check in the document if it contains diferrent account assignments like both cost center and internal order. In this case both cost center and order must belong to same company code.
    If you find the document fine, then solution is to change the error to warning using T Code OBA5 and application area KI (I assume). You should be seeing application area as part of your error message number which is usually first 2 characters.
    Regards
    Sreenivas

  • Delivery and shipment belong different company code

    Hi all,
    I do shipment via transportation planning point that has different company code to delivery order. the shipment can be done, but when i was doing for shipment cost, there's an error, that said "delivery and shipment belong different company code". can you help me, what happen with this?
    best regard,
    Hendry

    Hi Hendry,
    Please read SAP online help about this:
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/0b/f2ee344ecf11d2bf760000e8a7386f/frameset.htm
    Regards,
    Csaba

Maybe you are looking for