Credit memo for Inter-company billing

Hi
We are trying to create a credit memo with reference to an inter company billing document. The business requirement is to create a credit memo  to adjust the invoice value due to wrong value posted in the original inter-company invoice. Hence we do not want to use the sales returns route for this.
So, we are trying to create a credit memo request (ZCR) in VA01 with reference to the Inter company billing document (ZIV). We have maintained the copy control between ZCR and ZIV.
However, when creating a credit memo request (ZCR) with respect to the intercompany billing document, we get the below error in the sales order.
"Item category ZNLC is not defined" and "Check Item copy" with Message No: V1324.
ZNLC is the item category that we used in the intercompany delivery document.
We are able to ignore this message in sales order screen and save the credit memo request in VA01 and also create credit memo (ZG2) in VF01.
Pl provide your inputs on whether we are missing any other configuration.
Regards,
John

Hi
I have maintained the item level copy control settings as below.
In the copy control (VTAF) between ZCR (Credit memo request) and ZIV (Inter company billing) at the item level for ZNLC (Inter company item category coming source document), the following setup has been maintained
Copying requirements : 303
Copy schedule lines : Blank
Pos / neg qty : Blank
Pricing type : D
Update doc flow : X
Do not copy batch : blank
Pl let me know if there are any other settings to be done in config.
Thanks,
John

Similar Messages

  • Re : Organizational data for inter-company billing

    Hi
         While doing intercompany settings (img - enterprice structure - SD - assign sales org - disribution plant)     i am getting the following error
    " Organizational data for inter-company billing
    missing in plant SUDA "
    How to solve.
    Thanks
    Anto

    Hi Anto,
      IMG check wheather you assing Supplying company sales area to Supplying plant.
    IMG->Saes&Dsitr -> Billing -> InterCompany Billing-> Assign Organizational unit by Plant
    Select Plant (supplying company) and assign Sales org, Distbn Channel and Division of supplying company.
    Regards,
    M.Manickam

  • Organizational data for inter-company billing missing in plant 2200

    Organizational data for inter-company billing missing in plant 2200

    Dear Siva,
           This may be related to incompleteness in the inter -company billing configuration settings so go through this IMG path then do the proper settings,
    SPRO>Sales and distribution>Billing>Inter company billing>Assign organisational units by plant, here you need to assign the Sales organisation,Distributional channel and Division (sales area) to the 2200 plant.
    Now you try
    I hope it will help you
    Regards,
    Murali.

  • Credit memo t for inter company bill-problem in acct posting

    Hi Guru's,
    Problem occured when intercompany prices were missing therefore was corrections made manually.but some invoices were blocked (no accounting docs generated).Strange is that one invoice got accounting docs and not blocked (same correction was made as for all)?
    Every thing is same except item Quantity and order dates.
    Error:Reversal of document 02v1 1370000207v2 2007v3 not possible in FI
    Message no. F5A 005
    Diagnosis:
    Item & v4 in accounting document 02 1370000207 2007
    was valuated with an open item foreign currency valuation.
    System Response:
    Document cannot be reversed.
    The diference between the correct one and other three is
    1.one additional Item partener function(transporter) added to blocked invoices.
    2.Profit segments are different.
    3.Reference division is present.
    PLease Help,Very Urgent.
    Thanks in Advance,
    Rao.

    Hi,
    Please refer to SAP  Note 892646 - VF11 Unable to cancel billing document: F5A005, extract of which is below.
    Try the solution proposed.
    Summary
    Symptom
    An SD billing document cannot be cancelled. Error message F5A 005 occurs during release to accounting.
    Other terms
    VF11, VF02, F5A005, currency valuation, LFACIF70, REVERSE_ITEMS, BSEG-BDIFF, BDIFF, BDIF2, BDIF3
    Reason and Prerequisites
    A foreign currency valuation in FI was carried out. As a result the fields BSEG-BDIFF, BSEG-BDIF2 or BSEG-BDIF3 have been filled in the FI document. If you then try to carry out the reversal of the billing document using transaction VF11, the system will use the new cancellation procedure and try to reverse the FI document. Error messsage F5A 005 is issued in LFACIF70 when any of the above fields are not zero.
    Additional information:
    BSEG-BDIFF is filled when running SAPF100 for Balance Sheet preparation valuation and currency type 10
    BSEG-BDIF2 is filled when running SAPF100 for Balance Sheet preparation valuation and currency type 30
    BSEG-BDIF3 is filled when running SAPF100 for Balance Sheet preparation valuation and a third local currency (defined in transaction OB22)
    Solution
    Please follow the instructions of note 339928 to solve the problem. Make sure that parameter 'rule_new_cancel' has the value B. This has to be set within USEREXIT_FILL_XKOMK1 in program LV60BU01.
    Alternatively for release > 4.5 it is possible to reset the valuation made with balance sheet preparation by creating a new valuation method in transaction OB59 with the RESET button flagged. Then run SAPF100 (trx f.05) with the exact same variant/paramenters that you used for your original run (with balance sheet preparation flag on again!!!). This will set the values of BSEG-BDIFF for the documents to zero.
    Please, make sure that under SELECTIONS - DOCUMENT NUMBER, you specify the one document number that has to be reversed now. THIS IS VERY IMPORTANT, OTHERWISE UNWANTED DOCUMENTS WOULD BE REVERSED, TOO.
    Header Data
    Release Status: Released for Customer
    Released on: 22.11.2005  10:07:45
    Priority: Recommendations/additional info
    Category: Consulting
    Primary Component: SD-BIL-IV Processing Billing Documents
    Secondary Components: FI-GL-GL-G Closing Operations / Period-End
    Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    SAP_APPL 46C 46C 46C  
    SAP_APPL 470 470 470  
    SAP_APPL 500 500 500  
    SAP_APPL 600 600 600  
    SAP_APPL 700 700 700 X
    Related Notes
    339928 - New cancellation procedure cannot be deactivated
    Rgds,
    Karthik T

  • Credit memo request for inter company bill-problem in acct posting

    Hi Guru's,
       Problem occured when intercompany prices were missing therefore was corrections made manually.but some invoices were blocked (no accounting docs generated).Strange is that one invoice  got accounting docs and  not blocked (same correction was made as for all)?
    Every thing is same except item Quantity and order dates.
    Error:Reversal of document 02v1 1370000207v2 2007v3 not possible in FI
    Message no. F5A 005
    Diagnosis:
    Item & v4 in accounting document 02 1370000207 2007
    was valuated with an open item foreign currency valuation.
    System Response:
    Document cannot be reversed.
    PLease Help,Very Urgent.
    Thanks in Advance,
    Rao.

    hi rao,
    first try to reset the cleared items by using FBRA and then try to reverse the document. Also check check if the reversal date is still open for posting or not.
    Pl get back with the status.
    Thanks
    Sadhu Kishore

  • Intrastat Report in ECC 6 for Inter Company Billing

    Hi Experts,
    Need your input.
    In business case, Company code A raise intercompany invoice on Company B for Goods deliverd by Co A directly to End customer of Co B.
    Since there is no actual Physical goods receipt by Company B, the intrastat report is not fetching any data as goods are directly delivered to End Customer by Co A.
    Can Somebody help me ..how can we customise...the Report so that Company B will have Goods Arrival Report data.

    Hi Anil,
    I am sorry , i can't get you. You mean abaper will enter temp data .. in Dev server not in PRD..
    What do u means by that... since we want this report in PRD...so ultimately the same report needs in PRD also...and u mean that abaper will create temp data in Dev server only...
    can u please be more elaborative...in steps..

  • Inter company Billing for service industry

    Hi,
    I never workded over inter company billing.Please suggest me what to do? I am in a service industry project where no delivery takes place.So how should i go about for intercompany billing configuration?
    Thanx in advance.
    Regardds,
    Satya

    Dear Satya,
    You can create the inter company bill with refrence to the service order
    To do inter company billing settings go through this IMG path
    IMG>Sales and Distribution>Billing-->Intercompany billing
    Process steps for normal inter company process with delivery.
    INTER COMPANY BILLING
    Definition:
    A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
    To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
    It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
    Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
    Sales organizations and plants assigned to each other need not belong to the same company code.
    In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
    PARTIES INVOLVED
    1) End Customer 2) Ordering Company code 3) Supplying Company Code.
    End customer:
    Customer who orders goods from the ordering company code.
    Ordering Company Code:
    Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
    Supplying Company Code:
    Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
    CONFIGURATION SETTINGS
    Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
    DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
    Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
    Assign Organizational units by Plant:
    Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
    Define Internal Customer Number By Sales Organization:
    Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
    Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
    Transaction Code: XD01
    The ordering sales organization is represented as Internal customer of Supplying company code.
    We need to create customer master in Account Group - Sold to Party and maintain minimum required financial & Sales Area data.
    This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
    PRICING:
    We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
    We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
    This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer. We maintain PR00 condition type to represent the ordering company code's price to the end customer.
    Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
    Eg: Sales Org. of Ordering company code + End customer + Material.
    We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    Pricing Procedure ICAA01is determined at Intercompany billing processing level.
    Pricing Procedure ICAA01 - Pricing Procedure for Inter company billing is assigned to the combination of: Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
    Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
    PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    In your requirenment there will not be delivery process in between service sales order and the intercompany bill so do the settings accordingly in the copy controls between service sales order type and inter company billing type.
    I hope this will help you,
    Regards,
    Murali.
    I hope this will help you,

  • Inter company Billing document not created

    Hi,
    I am in a service industry project where invoicing is done through order ,no delivery takes place.I have done configuration related to inter company billing like Assign inter company billing type to Order ,assign plant sales area and internal customer to the ordering Sales Organisation.
    After this we are able to invoice the external customer but when we are trying to create inter company billiing document through the same order a log is created which says"Item already fully invoiced"
    What should i do now?
    Plz suggest.
    Regards,
    Satya

    Luk we are using quantity contract and through that we do DP91 for resource related billing which generate a Billing Request where sales document category is L (debit memo request) and then we billed that billing request to the end customer.But when i again use that billing request for inter company billing system says "item is fully invoiced"
    Now tell me what should i do?
    Regards,
    Satya

  • Error while Doing Inter Company Billing.

    Hi All,
    I am getting error while doing Intercompany Billing.
    I have done all the assigment for Inter company Billing.
    Now i have done F2 invoice and was trying to do IV billing , the SAP gives error " Sales organization  is not defined".
    I am not able to trace the solution for this problem.
    If someone has face similar error or have idea abt this error,please revert back.
    -Akash

    Hello,
    there are many notes concerning your reuqest:
    543821     FAQ: cross-company processing                          
    338922     Analysis note for cross-company transactions (deliv    
    308989     Consultant note for cross-company transactions         
    109254     Customizing stock transport order Cross Company        
    I hope that the information are helpful.
    Regards
    Claudia
    If you are satisfied with the answer, please give Reward Points

  • Inter Company Billing and automatic booking to Vendor master.

    Hi,
    Wish you a Happy New year,,,,,,,
    We have done all the necessary configuration for generating Inter Company billing including the Cost booking to vendor Automatically.
    There are certain points where I need some help,
    1) During Idoc genration we are getting error related to Payment terms of Internal Customer.
    If the payment terms is immidiate then only an Idoc is getting generated,,,,,,,,, else it is throwing an error message " status 51", but according to our business requirements it may be for any days and this may also impact our aging analysis and cash flows.
    2) We have configured upto Third level of product hierarchy but while creating a contract if user maintains only upto first level, then release to account is not happening for inter company billing. Where as if user maintain upto third level there is no issue in the whole process of inter comapny billing.
    Kindly suggest us how to restrict user to maintain product hierarchy pto third level during the creation of contract.
    3) during the Inter company billing generation, if the internal customer is eligible for Tax exemption or tax booking, that is how to book the tax details to internal customer and also to vendor while booking the cost.Please let us know the logic for tax processign in Inter company billing and Idoc generation.
    Awaiting for a favourable reply and thanks in Advance.
    Regards,
    Upendra.

    Hello,
    Did you assign the internal customer to the ordering sales organisation? If not, then create a customer in Delivering Sales org + DC+ Div + Plant and assign the same in the ordering sales organisation.
    You can maintian the same in SPRO --> Enterprise structure --> Defenition --> Sales organisation (Enter internal customer).
    Or
    SPRO--> Sales and  Distribution --> Billing ---> Intercompany billing --> Define internal customer
    Prase

  • Inter - company Billing - Assign Organisational units by plant

    Hi Experts
    Im posting this since I found the same question closed, unanswered.
    We are on IS - Retail and I have done all configuration for Inter-company Billing. However when I create the inter-company billing document I get the following error, "Sales organization & is not defined"
    I checked SAP note 308989 in which it says the delivering plant (Site) needs to be attached to both the Ordering and Delivering companies Sales organisation, Distribution channel combination. Also this needs to be done as part of master data in WB02, which I have done.
    It also says that the 2 entries maintained should be present in the table in transaction OVV9 - Assign Organisational units by plant. However, in my case the attachment of the site to the ordering companies sales org. is missing in the inter-company set up. Also it does not give the option of creating a new entry.
    Appreciate if someone could help me resolve this so I could create the inter company invoice.
    Thank you,
    Afzal

    Hi Afzal,
    in all the customizing setting of note 308989 are good, then those fields should be filled.
    Please check it very carefully.
    Please check in customizing of sales order type (transaction VOV8) if the intercompany billing type maintained.
    In case of stock tranfer order intercompany (where there is not sales order), run transaction 0VLK, display the delivery type used, and check the order type present in field 'Default Ord.Ty.' (usually it is 'DL').
    Then check in VOV8 for this sales order type.
    If everything is fine, then it is necessary to debug the delivery creation.
    The field LIKP-VKOIV etc. should be filled in program FV50XFLK_LIKP_FUELLEN_IV in intercompany sales; program FV50XFLK_LIKP_FUELLEN_IV_UML in stock transfer order intercompany.
    Best regards,
    Ivano.

  • Inter company billing use and steps?

    Inter company billing use and steps?

    INTERCOMPANY BILLING
    Definition:
    A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
    To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
    It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
    Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
    Sales organizations and plants assigned to each other need not belong to the same company code.
    In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
    PARTIES INVOLVED
    1) End Customer   2) Ordering Company code 3) Supplying Company Code.
    End customer:
    Customer who orders goods from the ordering company code.
    Ordering Company Code:
    Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
    Supplying Company Code:
    Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
    CONFIGURATION SETTINGS
    Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
    DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
    Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
    Assign Organizational units by Plant:
    Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
    Define Internal Customer Number By Sales Organization:
    Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
    Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
    Transaction Code: XD01
    The ordering sales organization is represented as Internal customer of Supplying company code.
    We need to create customer master in Account Group – Sold to Party and maintain minimum required financial & Sales Area data.
    This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
    PRICING:
    We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
    We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
    This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer.
    We maintain PR00 condition type to represent the ordering company code’s price to the end customer.
    Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
    Eg: Sales Org. of Ordering company code + End customer + Material.
    We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
    Condition records for PI01 are created with the following key combination:
    Ordering sales Org + Supplying Plant + Material
    Pricing Procedure ICAA01is determined at Intercompany billing processing level.
    Pricing Procedure ICAA01 – Pricing Procedure for Inter company billing is assigned to the combination of:
    1)     Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
    Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
    PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
    PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
    The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
    Condition Type VPRS in the intercompany-billing document indicates cost to the supplying company code.
    The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
    ILLUSTRATION:
    STEP 1: Create Sales Order
    Manually Enter the Delivery Plant of the Supplying Company Code:
    OBSERVE CONDITIONS SCREEN FOR ITEM:
    PR00 represents Price to the end customer (in other words, revenue for the ordering company).
    PI01 represents cost to ordering company (in other words, revenue for the supplying company). It is represented as statistical item only.
    DELIVERY:
    Delivery is carried out from the supplying point & hence we can observe that it is done from shipping point assigned to the supplying point.
    Subsequently, Picking & PGI are carried out.
    BILLING TO END CUSTOMER:
    T-Code: VF01
    Create Intercompany Billing:
    T-code: VF01
    OBSERVE THE CONDITIONS SCREEN OF THE INTERNAL INVOICE:
    IV01 Condition type represents revenue for the supplying company code.
    VPRS condition type represents cost to the supplying company code.
    PR00 in intercompany billing document displays amount billed to the end customer. It serves as just an information item and is inactive.
    If the ordering company enters the incoming invoice manually, the delivering company can print out an invoice document with the help of output type RD00, which is then sent to the Payer.
    If automatic invoice receipt has been agreed, we must use the SD output control functions to ensure that output type RD04 is found in internal billing. In R/3 system, output determination procedure V40000, which includes this output type, is assigned to Intercompany billing type IV.
    The automatic posting to the vendor account is initiated when output type RD04 is processed. The system uses the EDI output type INVOIC in the FI variant.
    To ensure that payables are posted in financial accounts of the ordering company, the delivery company must be created as a vendor.
    Configure Intercompany Stock Transport Order
    Material should exist in both the plants (Delivering  & Ordering),
    Internal customer should be assaigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.
    Assign its Sales area to the delivering plant
    Assign the document type and Delivery type  NB and NLCC
    Assign the Supplying plant --> Receiving Plant --> NB 
    Take the delivering plant and assign the sales area.
    Vendor master has to be created and assaign the supply source ( Delivering Plant).
    Create a puchase order ME21N ---> Save
    Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number here and execute.
    Select the Delivery creation line and do the back ground process.
    Start the log display and see the delivery document number by the documents button
    Goto VL02N --> do picking and PGI --> Then do the MIGO with

  • 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

  • Inter Company billing issues with product heirarchy

    Hi,
    Wish you a Happy New year,,,,,,,
    We have done all the necessary configuration for generating Inter Company billing including the Cost booking to vendor Automatically.
    There are certain points where I need some help,
    1) During Idoc genration we are getting error related to Payment terms of Internal Customer.
    If the payment terms is immidiate then only an Idoc is getting generated,,,,,,,,, else it is throwing an error message " status 51", but according to our business requirements it may be for any days and this may also impact our aging analysis and cash flows.
    2) We have configured upto Third level of product hierarchy but while creating a contract if user maintains only upto first level, then release to account is not happening for inter company billing. Where as if user maintain upto third level there is no issue in the whole process of inter comapny billing.
    Kindly suggest us how to restrict user to maintain product hierarchy pto third level during the creation of contract.
    3) during the Inter company billing generation, if the internal customer is eligible for Tax exemption or tax booking, that is how to book the tax details to internal customer and also to vendor while booking the cost.Please let us know the logic for tax processign in Inter company billing and Idoc generation.
    Awaiting for a favourable reply and thanks in Advance.
    Regards,
    Upendra.

    Double click the status 51 to find the error message. 51 just tells that the Idoc has an error, but which error can only be seen if you go a step more into detail.
    For what reason do you have level 1 product hierarchies in the system, if you need the full hierarchy to level 3?
    I give you example:
    Level 1 =11111
    level 2 = 21111, and 22222 and 23333
    level 3 = 31111 and 32222 and 33333
    Hierarchy should only be maintained available in customizing only in its full length:
    111112222233333
    or 111112111131111
    but not the level one alone.

  • Want to know about inter company billing or stock transfer

    Dear All,
    I want detail about intercomany billing. Currently we are not suing this std. flow. I want to study and implent. Pl. help  me in this process.
    Points will be added.
    Nik

    Hi ,
    Below is the interco. process.
    Business case: - Customer orders goods to company code/Sales organization A (Eg.1000/1000). Sales org 1000 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.2000/2000) will deliver the goods to end customer and raise an inter-company billing on C.Code/Sales Org 1000 with reference to delivery. This can happen only after 1000 raises invoice to his end customer to whom the material has been delivered by 2000.
    SPRO Customization required:-
    1. Assign plant of delivering company code to sales org/distribution channel combination of ordering company code (Enterprise structure -->Assignment --> S&D --> Assign Sales org, Dist channel to Plant)
    2. Assign intercompany billing type as IV for sales document type OR (S&D -->Billing --> Interco Billing -->Define order types for inter.co billing)
    3. Assign Organizational Units By Plant (S&D -->Billing --> Interco Billing -->Assign Org Units by Plant)
    4.Define Internal Customer Number By Sales Organization (S&D -->Billing --> Interco Billing -->Assign Org Units by Plant)
    5. Automatic posting to vendor account (Optional)
    6. Maintain pricing procedure determination -For customer sales and billing
    Maintain pricing procedure determination - For inter-company billing (interco price procedure ICAA01)
    Master data to be maintained:-
    1. Create end customer master in company code/sales org
    2. Create customer master for 1000 company code/sales org in sales area for 2000
    3. Maintain PR00 as price for end customer-Active in standard pricing procedure RVAA01
    4. Maintain PI01 as price which has to be paid to 2000-Statistical in RVAA01
    5. Maintain IV01 as inter-company Price-Active in ICAA01 
    Process:-
    1. Create OR with sold to party as end customer.
    2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as inter-company sales.
    3. Pricing procedure is RVAA01
    4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.
    5. Ordering sales org will create billing document F2 with reference to delivery for end customer.
    6. Delivering sales org will create inter-company billing IV with reference to delivery document.
    Hope this helps.

Maybe you are looking for