Inter Company Reports

I am looking for an SAP standard report that will show IC receovable and Payables between multiple companies. I will then use this information for external consolidation purposes.

Hi,
      Thanks for the response. However, this question is not related to the Fixed Asset issue, which has already been resolved.
Basically, we have two companies that are buying and selling between each other. One of the companies is a subsidery of the other. So, the parent(x) can sell or buy from it's sub(Y) and visa versa. At the end of the period, we need to consolidate both companies for reporting purposes, therefore there will be elimination entries which should be identified.
I need an SAP standard report to show these transactions which might still be sitting on each other books unsold.
Thanks

Similar Messages

  • SAP standard report to show Inter Company transactions

    Basically, we have two companies that are buying and selling between each other. One of the companies is a subsidery of the other. So, the parent(x) can sell or buy from it's sub(Y) and visa versa. At the end of the period, we need to consolidate both companies for reporting purposes, therefore there will be elimination entries which should be identified.
    I need an SAP standard report to show these transactions which might still be sitting on each other books unsold

    Dear :
                   We are using ECC 6 SAP version and we have the t code FBU3  for displaying all inter company transactions. Have you done necessary configuration in OBYF. You can display all related inter company transactions through FBU3.
    Your 2nd query corresponds to same credit control area that was assigned to two company codes. In order extend credit limit for a customer who is extended on two company codes which have same credit area. It is not possible you distinguish credit limit for a customer who is extended on two company codes having same credit control areas. CCA is defined at organization structure level and for the distinction you will have to define new credit control area in customization at
    enterprise level i-e
    Enterprise Structure.... Definition.... Financial accounting....define credit control area
    Assignment.....Assign credit control area to co code
    Do necessary customization for SD module
    and then in credit management for AR you will have to assign the credit control area to company codes i-e
    Account Recv/A/c Payable.....Credit Management.... Assign permitted CCA to Co code
    . This is the only way to to segregate customer credit limit for two company codes. Please revert in case of any confusion.
    Regards

  • Segment Reporting.... What happens to Inter Company Transactions

    I have 2 simple questions, please help me if you know the answers:
    1. Inter Company: When we report at Segment Level (ECC 6.0) how do we eliminate Intercompany sales for company codes belonging to same segment. Is there a standard program to do this.
    2. Inter Segment: Are there any standard reports for Inter Segment.
    Please do share you experiences with Inter Company and Inter Segment scenarios and reporting.
    Thanks

    The problem is you need to create  COMPANY and assign the same to both company codes in OBY6.
    The following information must be useful.
    You can post the cross company code postings even between two controlling areas. The system does not prevent to post documents between two company codes in two controlling area. Need not necessarily they should be under one operating concern. Provided you have to make sure that you have followed the following points:
    In OBY6 - To company codes must be assigned to same Company, meaning that you mus thave created a Company and that company must have been assigned to these two company codes.
    OBYA - You should maintain the clearing accounts in both the company codes. Meaning that you are posting one leg in one company code and the other leg in the other company. Therefore, it is required to have the missing legs in each company code.
    Company Code1 - Posting Key 40 - Clearing Account
    Company Code1 - Posting Key 50 - Clearing Account
    Company Code2 - Positng Key 40 - Clearing Account
    Company Code2 - Posting Key 50 - Clearing Account
    OB08 - In case if the two company codes have different local (company code) currencies, you may maintain the exchange rates.
    You can now go to F-02 and post a cross company code transaction giving the first leg in first company code and the second leg in second company code. Missing leg in the first company code will be posted to the GL Account mentioned in OBYA and the missing leg in the second company code will be posted to the GL Account mentioned in OBYA. That means you will have four line items overall.
    The system will post three document.
    Document 1 in First Company Code
    Document 2 in Second Company Code
    and
    Document3 - Cross Company Code Document.
    The cross company code document consists of the first company code document number plus company code plus last two digits of the fiscal year.
    Hope this must have clarified your doubts.
    Please let me know in case if you need further details.
    Thanks,
    Ravi

  • Order related Inter-company Billing (Third Party Order)

    Hi SAP Gurus,
    We are using SAP R/3 4.6C version.  Normally, the inter-company billing are delivery related and this is working fine.  I am configuring the order related Inter-company billing, i.e. Third Party drop shipment  with Inter-company.  I refered to SAP notes 203876, 63459, 381042 and maintained the copy control between OR => IVA (for TAS) as follows:
    Copying requirement      = '013',
       Invoiced quantity        = 'F', (*)
       Quantity/value          = '+',
       Pricing type            = 'G'.
    The issue I am facing is when I try to create an Inter-company invoice (after the F2 Customer invoice), the End customer details is being pulled instead of the Inter-company customer details.  In other words the Inter-company invoice is also being issued to the End customer.  Also the prices are showing in negative.
    Kindly share with me if any of you guys know a solution for this.  I have searched all the SAP forums, but couldn't find a similar issue.
    My concern here is, in none of the SAP notes, there is no information about the copying requirement at the header level between OR=>IVA.  I am not sure whether this is causing the issue.
    Regards,
    Saravanan

    Hello Mrinal,
    Please review the note 381042 Order-related intercompany billing in Releases.
        o  Report RVIVAUFT instead of report ZZIVAUFT
        o  Standard requirement 036 'Item/order related IB'
           Use this requirement in the copying requirement for billing
           documents for your process flow.
        o  Standard requirement 018 'Order-related IB' instead of
           customer-specific output requirement 990.
           Use this requirement in the output determination procedure of
           your billing documents (in the standard system, this is procedure
           V10000 'Billing outputs') for output type RDIV.
        o  Standard ouptput type RDIV instead of customer-specific output
           type ZZIV.

  • How to track Inter Company Asset Retirements

    Hi friends,
    We have a unique requirement. As opposed to normal inter-company asset transfers in SAP via ABT1N, we would like to retire the asset to an external company code. This would reflect as a retirement in the asset register, and not as a transfer. What we want to do is to track these Asset Transfers via some report.
    Are there any transactions in SAP that could be utilised to facilitate this scenario?  Please keep in mind that we won't use ABT1N, we will retire the asset via some other transaction, maybe F-92, or through P.O., and then would want to track such retirements through a report, exclusively. Please do suggest if some customisation can be done.
    Regards,
    Varun

    Hi Mukhtar.
    We have to develop a new report as none of the existing reports satisfy the criteria. Just wanted to know if someone has experience of developing it.
    Regards,
    Varun

  • No Company Code Track in Inter Company Code Transactions

    Hi,
    When we post an inter company code transaction system generates two documents in Both company codes involved in the transaction and an internal auto generated cross company code document number. But when i view these documents i am unable to see from which company receivable is standing and two which company payable is standing. it only shows in which company code the transaction was posted but no information is being provided against line item so that we can see on which company behalf have we booked or paid the expense. we are posting inter company code transaction through f-02. is there any other specific transaction code for this? or any report or any other way to view how much from which company is recyclable/Payable standing? please also not that we are using two different g/l for inter company receivable and payable.
    Regards,

    hi ,
    Can you please post the screen shot of one of those document . IF i am not wrong you want to know that  in which company ocde it posted . YOu can  find out from the Number range and then Comapny code in Docuemnt number .( In this Trading Partner poplauted Automatically) So definately you need Tranding partner  to do intercomapny reconciliation
    IF you have Cross comapny code Transaction you will have cross comapny  docuemnt number in FB03 as below which you can see in FBU3 .
    Sometime  you do not post Cross company transaction but you post in Individual companies with trading Partner .
    in this case there will not be any cross company document .. Please check your OBYA configuration and check which GL code you have defined and whether you have maintaned the config tfor that

  • Inter-company configuration

    Hello All,
    I'm looking for inter-company configuration and there reporting, where two companies are in different country and legal reporting requirements.
    Can any one help me in this regards,
    It will be appreciated, For your help.
    thanks,
    supriya.

    Have you reviewed Intercompany Reconciliation background  documentation?
    [Note 1164059 - ICR: Technical documentation and background information|https://websmp230.sap-ag.de/sap(bD1lcyZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1164059]
    I hope this helps.

  • Inter Company Stock transport order - invoice posting

    Hello,
    I have a group of materials getting delivered from one plant to another plant and both the plants are in different company codes. Both the plants are in different company codes and so we adopted inter company STO process.
    The STO process works fine with out failure. But during goods issue and invoicing some of the materials stock and amount values are getting posted differently than what is listed in PO.
    Our end user complains that goods receipt is OK but sap goods issue and invoiced too much.
    I tried looking at the purchase order history and every thing looks fine. When I look at the pricing conditions, I see one of the pricing condition is displayed with a red radio tab ( indicating a failure) but this pricing condition is not adding any amount to PO.
    The end user runs the customized MM report  to correct these issues.
    Can some one explain why their is difference showing up during invoice and goods issue time.
    Thanks
    Rakesh

    This could you be material price diffrent in both companey codes.Check the VL03N post goods issue material document accounting doument and check th Billing document in vf03 transaction accounting document.It seems in invoice some extra conditions added in your case.Chack MM invoice through MIR4 invoice.
    Normally when inter companey sto you have to do sales invoice and it will generate Miro invoice background.Check these things you will get some clue.

  • Inter Company Business Process Overview

    Hi,
    Could someone provide explanation on
    1. Inter Company Business Process / accounting
    2. Consolidation process
    Points would be assigned for satisfactory answers.
    regards
    Shankar

    Dear Shankar,
    1. Inter Company Business Process / accounting
       This involves inter company transaction amongst the Group.
    This may be in relation to the following.
    1. Common Debtors/Vendors
    2. Investments
    3. Inter company deposits and transfers of funds
    4. Inter company transfers of stock
    etc.
    2. Consolidation process
    In case of consolidation process entire listed above categories are added up for totalling them at a Group level or Company level.
    So in short these two are interrelated. At the time of consolidation all inter company debts are set off for making a consolidated balance sheet for reporting purposes.
    Hope this answers your question
    Deven.

  • Inter active report objects

    i want a beautiful inter active report  object based on SD module help me one.

    REPORT ZZ_22038_22098_002 NO STANDARD PAGE HEADING LINE-SIZE 650
    MESSAGE-ID ZZ_9838 .
    TYPE-POOLS: SLIS.
    *type declaration for values from ekko
    TYPES: BEGIN OF I_EKKO,
    EBELN LIKE EKKO-EBELN,
    AEDAT LIKE EKKO-AEDAT,
    BUKRS LIKE EKKO-BUKRS,
    BSART LIKE EKKO-BSART,
    LIFNR LIKE EKKO-LIFNR,
    END OF I_EKKO.
    DATA: IT_EKKO TYPE STANDARD TABLE OF I_EKKO INITIAL SIZE 0,
    WA_EKKO TYPE I_EKKO.
    *type declaration for values from ekpo
    TYPES: BEGIN OF I_EKPO,
    EBELN LIKE EKPO-EBELN,
    EBELP LIKE EKPO-EBELP,
    MATNR LIKE EKPO-MATNR,
    MENGE LIKE EKPO-MENGE,
    MEINS LIKE EKPO-MEINS,
    NETPR LIKE EKPO-NETPR,
    END OF I_EKPO.
    DATA: IT_EKPO TYPE STANDARD TABLE OF I_EKPO INITIAL SIZE 0,
    WA_EKPO TYPE I_EKPO .
    *variable for Report ID
    DATA: V_REPID LIKE SY-REPID .
    *declaration for fieldcatalog
    DATA: I_FIELDCAT TYPE SLIS_T_FIELDCAT_ALV,
    WA_FIELDCAT TYPE SLIS_FIELDCAT_ALV.
    DATA: IT_LISTHEADER TYPE SLIS_T_LISTHEADER.
    declaration for events table where user comand or set PF status will
    be defined
    DATA: V_EVENTS TYPE SLIS_T_EVENT,
    WA_EVENT TYPE SLIS_ALV_EVENT.
    declartion for layout
    DATA: ALV_LAYOUT TYPE SLIS_LAYOUT_ALV.
    declaration for variant(type of display we want)
    DATA: I_VARIANT TYPE DISVARIANT,
    I_VARIANT1 TYPE DISVARIANT,
    I_SAVE(1) TYPE C.
    *PARAMETERS : p_var TYPE disvariant-variant.
    *Title displayed when the alv list is displayed
    DATA: I_TITLE_EKKO TYPE LVC_TITLE VALUE 'FIRST LIST DISPLAYED'.
    DATA: I_TITLE_EKPO TYPE LVC_TITLE VALUE 'SECONDRY LIST DISPLAYED'.
    INITIALIZATION.
    V_REPID = SY-REPID.
    PERFORM BUILD_FIELDCATLOG.
    PERFORM EVENT_CALL.
    PERFORM POPULATE_EVENT.
    START-OF-SELECTION.
    PERFORM DATA_RETRIEVAL.
    PERFORM BUILD_LISTHEADER USING IT_LISTHEADER.
    PERFORM DISPLAY_ALV_REPORT.
    *& Form BUILD_FIELDCATLOG
    Fieldcatalog has all the field details from ekko
    FORM BUILD_FIELDCATLOG.
    WA_FIELDCAT-TABNAME = 'IT_EKKO'.
    WA_FIELDCAT-FIELDNAME = 'EBELN'.
    WA_FIELDCAT-SELTEXT_M = 'PO NO.'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'IT_EKKO'.
    WA_FIELDCAT-FIELDNAME = 'AEDAT'.
    WA_FIELDCAT-SELTEXT_M = 'DATE.'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'IT_EKKO'.
    WA_FIELDCAT-FIELDNAME = 'BUKRS'.
    WA_FIELDCAT-SELTEXT_M = 'COMPANY CODE'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'IT_EKKO'.
    WA_FIELDCAT-FIELDNAME = 'BUKRS'.
    WA_FIELDCAT-SELTEXT_M = 'DOCMENT TYPE'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'IT_EKKO'.
    WA_FIELDCAT-FIELDNAME = 'LIFNR'.
    WA_FIELDCAT-NO_OUT = 'X'.
    WA_FIELDCAT-SELTEXT_M = 'VENDOR CODE'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    ENDFORM. "BUILD_FIELDCATLOG
    *& Form EVENT_CALL
    we get all events - TOP OF PAGE or USER COMMAND in table v_events
    FORM EVENT_CALL.
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
    I_LIST_TYPE = 0
    IMPORTING
    ET_EVENTS = V_EVENTS
    EXCEPTIONS
    LIST_TYPE_WRONG = 1
    OTHERS = 2
    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. "EVENT_CALL
    *& Form POPULATE_EVENT
    Events populated for TOP OF PAGE & USER COMAND
    FORM POPULATE_EVENT.
    READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'TOP_OF_PAGE'.
    IF SY-SUBRC EQ 0.
    WA_EVENT-FORM = 'TOP_OF_PAGE'.
    MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
    WA_EVENT-FORM.
    ENDIF.
    READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'USER_COMMAND'.
    IF SY-SUBRC EQ 0.
    WA_EVENT-FORM = 'USER_COMMAND'.
    MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
    WA_EVENT-NAME.
    ENDIF.
    ENDFORM. "POPULATE_EVENT
    *& Form data_retrieval
    retreiving values from the database table ekko
    FORM DATA_RETRIEVAL.
    SELECT EBELN AEDAT BUKRS BSART LIFNR FROM EKKO INTO TABLE IT_EKKO.
    ENDFORM. "data_retrieval
    *& Form bUild_listheader
    text
    -->I_LISTHEADEtext
    FORM BUILD_LISTHEADER USING I_LISTHEADER TYPE SLIS_T_LISTHEADER.
    DATA HLINE TYPE SLIS_LISTHEADER.
    HLINE-INFO = 'this is my first alv pgm'.
    HLINE-TYP = 'H'.
    ENDFORM. "build_listheader
    *& Form display_alv_report
    text
    FORM DISPLAY_ALV_REPORT.
    V_REPID = SY-REPID.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_CALLBACK_PROGRAM = V_REPID
    I_CALLBACK_PF_STATUS_SET = ' '
    I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
    I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
    I_GRID_TITLE = I_TITLE_EKKO
    I_GRID_SETTINGS =
    IS_LAYOUT = ALV_LAYOUT
    IT_FIELDCAT = I_FIELDCAT[]
    IT_EXCLUDING =
    IT_SPECIAL_GROUPS =
    IT_SORT =
    IT_FILTER =
    IS_SEL_HIDE =
    i_default = 'ZLAY1'
    I_SAVE = 'A'
    is_variant = i_variant
    IT_EVENTS = V_EVENTS
    TABLES
    T_OUTTAB = IT_EKKO
    EXCEPTIONS
    PROGRAM_ERROR = 1
    OTHERS = 2
    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. "display_alv_report
    *& Form TOP_OF_PAGE
    text
    FORM TOP_OF_PAGE.
    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
    IT_LIST_COMMENTARY = IT_LISTHEADER
    i_logo =
    I_END_OF_LIST_GRID =
    ENDFORM. "TOP_OF_PAGE
    *& Form USER_COMMAND
    text
    -->R_UCOMM text
    -->, text
    -->RS_SLEFIELDtext
    FORM USER_COMMAND USING R_UCOMM LIKE SY-UCOMM
    RS_SELFIELD TYPE SLIS_SELFIELD.
    CASE R_UCOMM.
    WHEN '&IC1'.
    READ TABLE IT_EKKO INTO WA_EKKO INDEX RS_SELFIELD-TABINDEX.
    PERFORM BUILD_FIELDCATLOG_EKPO.
    PERFORM EVENT_CALL_EKPO.
    PERFORM POPULATE_EVENT_EKPO.
    PERFORM DATA_RETRIEVAL_EKPO.
    PERFORM BUILD_LISTHEADER_EKPO USING IT_LISTHEADER.
    PERFORM DISPLAY_ALV_EKPO.
    ENDCASE.
    ENDFORM. "user_command
    *& Form BUILD_FIELDCATLOG_EKPO
    text
    FORM BUILD_FIELDCATLOG_EKPO.
    WA_FIELDCAT-TABNAME = 'IT_EKPO'.
    WA_FIELDCAT-FIELDNAME = 'EBELN'.
    WA_FIELDCAT-SELTEXT_M = 'PO NO.'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'IT_EKPO'.
    WA_FIELDCAT-FIELDNAME = 'EBELP'.
    WA_FIELDCAT-SELTEXT_M = 'LINE NO'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'I_EKPO'.
    WA_FIELDCAT-FIELDNAME = 'MATNR'.
    WA_FIELDCAT-SELTEXT_M = 'MATERIAL NO.'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'I_EKPO'.
    WA_FIELDCAT-FIELDNAME = 'MENGE'.
    WA_FIELDCAT-SELTEXT_M = 'QUANTITY'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'I_EKPO'.
    WA_FIELDCAT-FIELDNAME = 'MEINS'.
    WA_FIELDCAT-SELTEXT_M = 'UOM'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    WA_FIELDCAT-TABNAME = 'I_EKPO'.
    WA_FIELDCAT-FIELDNAME = 'NETPR'.
    WA_FIELDCAT-SELTEXT_M = 'PRICE'.
    APPEND WA_FIELDCAT TO I_FIELDCAT.
    CLEAR WA_FIELDCAT.
    ENDFORM. "BUILD_FIELDCATLOG_EKPO
    *& Form event_call_ekpo
    we get all events - TOP OF PAGE or USER COMMAND in table v_events
    FORM EVENT_CALL_EKPO.
    CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
    I_LIST_TYPE = 0
    IMPORTING
    ET_EVENTS = V_EVENTS
    EXCEPTIONS
    LIST_TYPE_WRONG = 1
    OTHERS = 2
    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. "event_call_ekpo
    *& Form POPULATE_EVENT
    Events populated for TOP OF PAGE & USER COMAND
    FORM POPULATE_EVENT_EKPO.
    READ TABLE V_EVENTS INTO WA_EVENT WITH KEY NAME = 'TOP_OF_PAGE'.
    IF SY-SUBRC EQ 0.
    WA_EVENT-FORM = 'TOP_OF_PAGE'.
    MODIFY V_EVENTS FROM WA_EVENT TRANSPORTING FORM WHERE NAME =
    WA_EVENT-FORM.
    ENDIF.
    ENDFORM. "POPULATE_EVENT
    *& Form TOP_OF_PAGE
    text
    FORM F_TOP_OF_PAGE.
    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
    IT_LIST_COMMENTARY = IT_LISTHEADER
    i_logo =
    I_END_OF_LIST_GRID =
    ENDFORM. "TOP_OF_PAGE
    *& Form USER_COMMAND
    text
    -->R_UCOMM text
    -->, text
    -->RS_SLEFIELDtext
    *retreiving values from the database table ekko
    FORM DATA_RETRIEVAL_EKPO.
    SELECT EBELN EBELP MATNR MENGE MEINS NETPR FROM EKPO INTO TABLE IT_EKPO.
    ENDFORM.
    FORM BUILD_LISTHEADER_EKPO USING I_LISTHEADER TYPE SLIS_T_LISTHEADER.
    DATA: HLINE1 TYPE SLIS_LISTHEADER.
    HLINE1-TYP = 'H'.
    HLINE1-INFO = 'CHECKING PGM'.
    ENDFORM.
    FORM DISPLAY_ALV_EKPO.
    CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
    EXPORTING
    I_INTERFACE_CHECK = ' '
    I_BYPASSING_BUFFER = ' '
    I_BUFFER_ACTIVE = ' '
    I_CALLBACK_PROGRAM = V_REPID
    I_CALLBACK_PF_STATUS_SET = ' '
    I_CALLBACK_USER_COMMAND = 'F_USER_COMMAND'
    I_CALLBACK_TOP_OF_PAGE = 'TOP_OF_PAGE'
    I_CALLBACK_HTML_TOP_OF_PAGE = ' '
    I_CALLBACK_HTML_END_OF_LIST = ' '
    I_STRUCTURE_NAME =
    I_BACKGROUND_ID = ' '
    I_GRID_TITLE = I_TITLE_EKPO
    I_GRID_SETTINGS =
    IS_LAYOUT =
    IT_FIELDCAT = I_FIELDCAT[]
    IT_EXCLUDING =
    IT_SPECIAL_GROUPS =
    IT_SORT =
    IT_FILTER =
    IS_SEL_HIDE =
    I_DEFAULT =
    I_SAVE = 'A'
    IS_VARIANT =
    IT_EVENTS = V_EVENTS
    TABLES
    T_OUTTAB = IT_EKPO
    EXCEPTIONS
    PROGRAM_ERROR = 1
    OTHERS = 2
    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.
    regards
    aswin

  • Inter company billing relevancy - Question

    We have one order type (A) which we want to make it not relevant for inter company billing. The order type used to use the same delivery and intercompany billing type (ZIA) other order types (B, C...) which are relevant for inter company billing.
    We have removed the inter company billing type from the order type (A) definition. And we have added a requirement in copy control to stop the inter company billing from this order type (A).
    Now the inter company billing doc is not created any more due to the copy control requirement. But when I run billing due list, it still shows that the delivery for this order type(A) is relevant/due for inter company billing.
    I guess the reason is that since order type A shares that same delivery and billing doc type with other order types, the copy control from the delivery and billing (inter company) still shows the flow from the delivery to the inter company billing type is valid, thus still trying to create the inter company billing. (Since I cannot remove the copy control from the delivery type to the inter company type)
    So my questions are: Did I missing anything else to exclude this order type from inter company billing? Do I have to use a different set of delivery type to make the deliveru due list NOT to show that the deliveries for order type A are due for inter company billing?
    Thanks.

    Hi,
    I think that the next notes suggest a solution:
    Note 209934 - Reason f rejection ineffect w intercompany billing
    Note 308989 - Consultant note for cross-company transactions (and related notes)
    Note 338922 - Analysis note for cross-company transactions (delivery)
    Note 502877 - Delivery without reference relevant for intercompany billing
    Note 301254 - Creation of billing index
    Note 386370 - Check report for the billing due list (billing index)
    I hope this helps you,
    Regards,
    Eduardo

  • Problem with RDIV output for order related inter company billing

    Hi ,
    Developing a order related inter company flow . IC Billing (type IVA) gets generated through RVIVAUFT , but facing the following issues with output (though configuration has been done as per note 728993)
    system only creates SAP standard billing type IVA i.e not any ZIV2 which is a copy of IVA (Find IVA is hard coded in RVIVAUFT )
    why note 728993 says V10000 'Billing Output i.e why not V40000 // Intercompany billing
    No document flow on IVA billing generated through RVIVAUFT. It does not show its link with original sales order .
    It will be very good if someone Thanks
    With regards,
    Mrinal

    Hello Mrinal,
    Please review the note 381042 Order-related intercompany billing in Releases.
        o  Report RVIVAUFT instead of report ZZIVAUFT
        o  Standard requirement 036 'Item/order related IB'
           Use this requirement in the copying requirement for billing
           documents for your process flow.
        o  Standard requirement 018 'Order-related IB' instead of
           customer-specific output requirement 990.
           Use this requirement in the output determination procedure of
           your billing documents (in the standard system, this is procedure
           V10000 'Billing outputs') for output type RDIV.
        o  Standard ouptput type RDIV instead of customer-specific output
           type ZZIV.

  • List of company for Consolidate detail in Inter-company

    Hi all,
    Do you have any idea how i could not see the list of company for Consolidate in inter-company?
    As the user guide from SAP, there is more field but my own is not.

    For the list of vendors for the material - Me03 if source list is maintained
    For list of vendors with info record - Me1m
    For list of vendors with PO - Me2l
    If you can give the correct requirements then your Technical consultant will develop a report in the required format.

  • Inter company stock orders

    In MD04, there are many MRP elements like Cus ord, ShpgNt and so many.
    CAn anybody please tell me which elements will constitue the sales orders and which will constitute the Inter company orders..
    I am in need of developing a report which says the sales orders for a material and Inter company stock orders in seperate columns..
    Please help me out..
    THanks
    Karthick P

    My question is different..
    I just want to know which of the MRP elements will combine to form the sales orders of a material and which will combime for Intercompany atock orders...
    Karthick p

  • Inter-company billing values flow to COPA

    Dear All,
    We are in inter-company sales scenario
    Issue -
    Sales persons have created two billing document with type F2 and IV
    Condition type PR00 and PI01 ( inter-comapny price ) assigned to COPA value field VVS04.
    Billing document F2 ( orderning plant ) - From sales order to accounting the net sales value has been updated as 0.17
    But COPA document is updated as 1.17 ( Net value 0.17+ cost 1 )
    But we require the value as 0.17
    In the above scenario FI & COPA are not getting reconcile
    Please throw some light on this
    Regards
    Madhu

    Hi
    It seems you have mapped both revenue and COGS to same value field..
    In COPA, all values are updated as absolute values i.e. without +/- sign except for billing reversals and credit memos...
    You should map both to separate value fields and show revenue- cost in reports
    Ajay M

Maybe you are looking for