Different currecny in intercompany billing

Hi Friends ,
My process flow is Purchase order - delivery - intercompany billing . In the PO currency is Newzeland dollor . Where as in the intercompany billing, it is picking up doc currency as USD, obviously from sold to party . I need to bill this in NZD only without changing the existing currency ( USD) in the sold to pary master record.
I tried with different options in ' Price Source' field in copy controls but it doesn't work .
How can I do that ?
Regards
Mahesh.

In this case the sold to party is a Plant , and billing would be majorly in USD . This is first time we need to bill in other currency and going forward we may have to use different currenies ( other than USD and NZD ) on quiet a few occassions . So we cannot afford disturb the sold to party master record .
What are the ways to about it ?
Regards
Venu

Similar Messages

Account assignment group is different in Intercompany Billing from Material Master

Hello,
Account assignment group is different in Intercompany Billing from Material Master.
Account assignment group in Billing and Intercompany Billing is feched from Material Master.
In Material Master, account assignment group is assigned as 12.
In Billing, account assignment group is 12 but in Intercompany Billing, account assignment group is 13.
Please help me to understand why in Intercompany Billing, account assignment group is 13.
Best Regards,
Debashri Dutta

Check the table MVKE for the values maintained for field KTGRM. You can see the sales org-DC combinations for which the AAG is maintained as 13 for this material. This may give you clues for investigation.

Error in intercompany billing

Hi all ,
the problem is that when making IV invoice I get error that the document is not relevant to billing.
But the F2 invoice I could make well.
Also I dont get the values of intercompany fields in LIKP table.
Where can be the problem?
Max points will be added if helpful.
Thanks and best regards
L

Hi,
Which process you followed?
See the Snote 308989- for different processes for Intercompany sales process
Thanks
Chidambaram

Issue with Intercompany billing- Third Party

Hi Gurus,
       I have a SD flow for intercompany billing the below is the problem with it:
Assume: X as customer and Y as vendor in with different company code but in same client
1) Let as X get PO(Purchase order) for 20 item from one person and it make SO(Sales Order) for that person.
2) Now X makes one PO and sends to Y via idoc and Y makes SO for X and does deilvery to that person and while deliverying there was a batch split in delivery with 10 and 10 items
3) Now when Y does MIGO and MIRO via idoc then as there were 2 line items in delivery and when invoice was made it also had 2 lines items.
4) Idoc failed at this point of time as in actual PO from X to Y there was 1 line item and in incoive there where 2 line items
5) And thus no account posting was possible.
    I have ask SAP and he suggest not to do the batch split and its not advisable.
   Please reply me with some solution so that I can get rid of this problem.
Regards,
Sagar

Hi
I feel when ever you raise the PO, kindly confirm with vendor whether there is any batch process, if yes kindly update the same, when you creating the PO, so that when ever your doing GRN(MIGO), it will shows the available batch for this PO.
If you follow the same, then the account document will be posted. better to mention the batch at PO level, or otherwise if avoid the batch, then it may affect the GRN(MIGO).
Reward if it helps
Regards
Prasanna R

Cross company Stock Transport with Intercompany billing

hi,
I'm trying to use the standard cross company stock transport order process, however, when i create the initail purchase order in the ordering company, the shipping tab does not appear, preventing me from creating a delivery. The customers and vendors have been assigned correctly. Can anybody help ???

dear govender
refer this
STO PROCESS
Stock Transfer Orders comes into picture when the stock is moving / Transferring between two different plants with two Different Company Codes or Stock Transfer between two plants with One Company Code the Difference are given below:
P.O Order types and Delivery Types
STO: - Stock Transfer Order Intra Company
Stock Transfer between Two Plants with One Company code.
The Purchase Order Type is Used in this case is "UB".
And the Delivery Type Used here is "NL".
Goods Movement type: 641
Item Category in delivery is NLN
STPO: - Stock Transfer Purchase Order Inter Company
Stock Transfer Purchase Orders between Two Plants with Two Different Company Codes.
The Purchase Order Type is Used in this case is "NB".
And the Delivery Type Used here is "NLCC".
Goods Movement type: 643
Item Category in delivery is NLC
A. Configure Intercompany Stock Transport Order
Material should exist in both the plants (Delivering & Ordering),
Internal customer should be assigned 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 assign the supply source (Delivering Plant).
Create a purchase order ME21N ---> Save
Delivery VL10 G ---> Calculation rule (appropriate) --> Assign 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 respect to the delivery document.
Billing (Intercompany pricing conditions should be set).
AND
1. Customer No. for the Goods Receiving Plant - OMGN
2. Availability Check- Checking Rule (if necessary) - OMGN
3. Assign a Delivery Type for the Delivering Plant - OMGN (for Stock Transport Orders, NLCC)
4. PO type (which i believe you have done) - OMGN
5. Assign Vendor No. to the Supplying Plant (done) - VK02
6. Assign Customer No. to the Purchasing Plant for the Inter-Company Invoice (but you need to assign this to the Sales Organization pre-assigned to the Purchasing Plant),
IMG-SD-Billing-InterCompany Billing-Define Internal Customer No. by Sales Org
***and by the way for the Invoice to work between Cross-Company Plants, you need also to have a Sales Org for the Supplying Plant and a Pricing Determination Procedure
INTERCOMPANY PRICING:
PI01 Intercompany: fixed amount per material unit
PI02 Intercompany: percentage of the net invoice amount
These condition types specify that the price charged by the delivering plant to the sales organization is shown as a statistical value in the sales order and an effective charge in the internal invoice.
The condition records you create and maintain for intercompany billing are the same kind of records that you create for pricing in general.
IV01 Inter-company Price ERLOS Revenue
IV02 Inter-company % ERLOS Revenue
STO CONFIG:
The following steps have to be followed in order to configure stock transport order between two plants.
1. Create a vendor for the Company code of the receiving plant using account group 0007 via T-Code XK01.
2. In the purchasing data view assign the supplying plant and the schema group
3. Create customer with the sales area of the vendor.
4. The shipping conditions, the delivering plant and the transportation zone determine the route in the STO.
5. In the pricing procedure determination relevant to the STO assign document pricing procedure and customer pricing procedure to get the pricing in the invoice.
6. Maintain condition records for pricing condition.
7. Maintain carrier as a partner in the customer master.
8. In OMGN select the supplying plant and assign the company code and sales area. Similarly select the receiving plant and assign the company code and sales area (The company code to which the plant is assigned to).
9. Assign the delivery type and checking rule to the document type.
10. And finally, assign the purchasing document type to the supplying plant and the receiving plant.
11. Create the STO using T-Code ME 21N and save.
12. Check for release strategy if any and release using T-Code ME 28.
13. Create delivery in background using VL10G.
14. If delivery is created, it is an indication of correct configuration and master data creation.
Stock transfer between two plants in different company codes is known as inter company stock transfer.
Material should be maintained in both supplying and receiving plant MM01
Stock should maintain only in supplying plant MB1C
Create receiving plant as a customer in supplying plants company code and sales area XD01
Assign this customer number in receiving plant details OMGN
Assign supplying sales area in supplying plant details OMGN
Assign delivery type NB for in combination of supplying/ receiving plants.
Create STO ME21N
As it is normal there in the item details we should get shipping date i.e. customer number
Go for Delivery VL10B
Shipping point *****
Select PO go for execute
then select the delivery then go for delvy ............create delvy,,,, delvy number generated.
Goods Issue VL02
Delvy doc **********
Click on picking
enter the picking qty
Click on PGI
in the mean time check in the PO history you will get the details
Goods receipt MIGO
Stock overview the stock will be updated....
Check the below link
http://help.sap.com/saphelp_47x200/helpdata/en/4d/2ba31643ad11d189410000e829fbbd/frameset.htm
Stock transfers that include deliveries and billing documents/invoices are only possible between plants belonging to different company codes.
If you want to carry out a cross-company-code stock transport order with delivery but without a billing document, you must set the Relevant for Billing (data element FKREL) indicator in Customizing of the item type to "blank" (Not relevant for billing).
The following applications are involved in this type of stock transfer:
Purchasing (MM-PUR) in entering the order
Shipping (LE-SHP) in making the delivery from the issuing plant
Billing (SD-BIL) in creating the billing document for the delivery
Inventory Management (MM-IM) at goods receipt in the receiving plant
Invoice Verification (MM-IV) at invoice receipt in the receiving
Transfer of goods from one location to another location, it may be between plants within the same company code or in different company code's plants.
within the company code, but plants,
receiving plant will raise the STO in Supplying/issuing plant-ME21n,
Supplying plant will deliver the goods to receiving plants ,
then we need to pick n post the Goods Issue-VL02n,
now when we can observe that the STO qty will be added into receiving plant and reduced in Delivering plant,
To do this, we need do prior customization in SPRO-IMG,-
material should be created in both plants( receiving & Supplying)
-maintain the stock only in supplying plant
-create a dummy customer in supplying plant's sales area(if u have one sales area, create in tat comp code n sales area)
-assign this customer number to receiving plant's details along with the sales area,
-Assign the STO doc type(UB) to Supplying plant, along with checking rule
-Assign the Del type (NL/NLCC) to Supplying n receiving plant.
*Del type=NL is not relevant for billing, where as NLCC is relevant for billing
rewards if it helps
siva

Intercompany billing with consignment client

Hello,
I have a question; did anybody have the same problem?
I'm doing an invoice in VF01 of an intercompany billing after having done a normal invoice to a costumer.
I'm having a consignment process in which I did the sales order from an sales organization and a plant from different company codes, then did the delivery and the invoice. When it comes to the intercompany billing invoice i get the error "Sales organization is not defined" and I did all the customizing defined in note 308989.
Can anybody give me a help please.
Thanks
Paula

Hi ,
Please check the following OSS notes:
Note 338922 - Analysis note for cross-company transactions (delivery)
Note 543821 - FAQ: Cross-company processing
Maybe when you compare info there with your system setup, you will find what is wrong.
Second thought - if you double click on the error message, does SAP suggest you what should be next steps ? Sometimes you can find helpful hints there.
Third thought - do you have all master data in appropriate sales organizations ?
Best regards
Witek

Intercompany billing Delivery to Billing document

Dear all,
I have scenario intercompany billing process where in the proces as follows
- customer billing is fine with 2 line items from different plants and i have 2 deliveries and i have 1 invoice
- when it comes to intercompany billing with the delivery related system is not picking the first line item but it is picking the 2nd line item only.
i need both the line items to appear in the intercompany billing document.
i have checked the copy control in VTFL, my settings are as follows
004 Deliv-related item
003 Single invoice
can any body suggest me a solution, this is very urgent for me
Thanks & Best Regards
Naveen

sorry my settings for the above scenario are
015 Itm dlv.rel.IC bill copy control
001 Inv.split (sample)
Thanks & Best Regards
Naveen

INTERCOMPANY BILLING & Contract

Dear guru
what is mean intercompany billing & Contract? and give me the steps to config. in sd module.
regards
Mohammedrenu
[email protected]

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.
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.
<b>Contracts</b>
Follow the links
http://help.sap.com/saphelp_47x200/helpdata/en/06/57683801b5c412e10000009b38f842/frameset.htm
Master Contract:
The master contract is a document under which you can group contracts as lower level contracts. It contains the general terms which apply for all the lower level contracts over a specified period.
Use
You group contracts as lower level contracts under a master contract to ensure that
The terms in the master contract are granted in all the lower level contracts
The data in all lower level contracts remains consistent
You can group the following documents under a master contract:
Quantity contracts
Value contracts
Service contracts
The link between the master and lower level contracts is controlled by the referencing procedure which is assigned to the master contract type in Customizing. The referencing procedure determines which data is copied from the master contract into the lower level contracts
Structure
A master contract contains header data only. In the master contract, you can record:
Business data
Partner data
Contract data
Billing plan data
On the overview screen of the master contract, there is a list of all the lower level contracts which refer to it. You can branch from this list into the individual contracts.
Master Contract: The master contract is a document under which you can group contracts as lower level contracts. It contains the general terms which apply for all the lower level contracts over a specified period.
Check these links on Master Contract
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd0d545a11d1a7020000e829fd11/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd34545a11d1a7020000e829fd11/content.htm
http://help.sap.com/saphelp_47x200/helpdata/en/dd/55fd27545a11d1a7020000e829fd11/content.htm
Details about contracts:
Lets take standard CQ contract type:
First maintain customer - material info record in VD51 T-code
Secondly maintain pricing for customer / material or only material combination in VK31 / VK11 T-code
Then use VA41 T-code to create a contract
VA42 to change contract
VA43 to display / view contract
In VA41, enter the document type CQ, followed by the sales area details,
Enter Sold to party.
Enter PO number
Enter PO Date
Enter Validitiy from Date
Enter Validity to Date
Enter Material
Enter Quantity say 999,999,999 or any other higher quantity as it is referred again and again
Hit Enter.
Save.
For further info refer below
: CONTRACTS
Contracts
Reward if Helpful...
Regards,
Praveen Kumar D

Intercompany billing currency

hi,
the default currency of intercompany billing is defaulted from customer master. however, sometimes the currecny should be changed, how can i do it if without the change currecny in customer amster
thanks

Hi Jo Jo
Only two ways currency can come. Customer master or condition records.
Now if u want to have currency other than this and this is needed to post the records to a G/L account then you can define the posting currency in the G/L (FS03).
Furthermore if u want to have some prints or email then you can define the output processing the program and the form for that currency.
Reward if helpful
Kind Regards
Sandeep

Intercompany billing document setup

Hi,
      I would like to enquire on intercompany billing document setup.
      We have customized billing type ZIV for intercompany invoice, and ZIG for intercompany credit memo.
       Is is possible to set up the cancellation for each billing type as
          - ZIG for ZIV and
          - ZIV for ZIG
min

Hello MIN,
For practice & understanding or test purpose, this can be ok.
But, in actual or real time scenario, I don't think it hold good.
See, you said ZIG is a Credit Memo for Inter-company right?
How you are going to use it for cancellation?
As I know, a Credit Note or Credit Memo is a document used to adjust or rectify errors made in a sales invoice which has already been processed and sent to a customer. If you have already sent an invoice to a customer but now need to provide a credit for that invoice, you would send them a Credit Note or Credit Memo. You can think of a credit note as a "negative invoice."
But not CANCELLATION INVOICE.
Logically, if you see, there will be a number range issue. So, just visualise, when you have to book an actual credit note, then what you are going to do? And how is you end user and auditor is going to recognize the credit memo?
For your your purpose of having a different cancellation doc for inter-company sales invoice and credit memo, you can create a Z Cancellation Billing Doc, say, ZIC and assign it to ZIV & ZIG billing Doc.
Hope it assist you.
Thanks & Regards
JP

Intercompany Billing and Delivering Plant

Hi,
I had selected a delivering plant for my intercompany billing, that was different from the one previously assigned to my sales organisation and company code. However, even after cancelling those assignments, I still cannot use my original plant to process sales orders.
I keep getting the error message" enter a valid delivering plant"
Could you tell me how to resolve this issue and oblige?
Regards,
Aditya

Hi,
check whther the assignemnt for intecompany settings. The Delivering plant should be asigned to the ordering Sales org and distribution channel combination.
Prasanth

Manual change / copy currency in intercompany billing document

Hi,
We are running the SD intercompany process, where 'F1' is the customer invoice billing document type and 'IV' is the intercompany billing document type.
The currency in billing document type 'F1' is derived from the final customer master data, whereas the currency in billing document 'IV' is taken from the intercompany customer master data. We would like the currency in billing document 'IV' (intercompany) to be the same as the one in 'F1'. It is the Finance team business requirement.
Is it possible to have the currency copied from 'F1' to 'IV'. We would also be happy to manually change the currency in 'IV'.
Please advise which settings are required - if this is even possible.
Thank you,
Karol
Edited by: Karol on Jun 17, 2010 12:07 PM

Hello Karol
Why do you want to get into copy controls etc,, when you can simply set up the Intercompany customer's currency based on the customer's (Sales Org) country.
Let me explain. US Company is selling to US customer from a Plant in Switzerland. Real customer is set up with USD in US sales area. The Inter Co Customer created in Swiss Sales Area should be set up with USD as currency based on the country of the Inter Co customer. This is how it is set up in my current client's setup and is working. The only issue you may get is when US is supplying to an International customer based in UK, then you will run into issues, I am assuming you don't have any such cases.
If the customer master set up idea does not work for you, then I guess your only option are user exits during Billing document creation or copy control routines.
Proposals:
1) USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC). Yo can try filling up VBRK-WAERK with VBAK-WAERK.
2) Alternately you may insert the same logic in Include LV60AA95 for program SAPLV60A. This is supposed to be part of the copy control routines but I don't know how it is called etc. It does not appear to be filled in the copy control config. I got the inspiration for this from OSS note 358893 which was meant for Euro conversion, Same concept so why not use it?
3)Thirdly in the area of copy control (Delivery- Billing Document) itself, for the item category, set up a custom routine in the feild Data VBRK/VBRP and insert code there to replace the Document currency with that from the sales order. You may also want to set up the PricingExchRate type field also with a suitable value right here itself. Only doubt is whether this works for only item or for header also as the field name (VBRK/VBRP) indicates.
Review the following OSS note 358893 - Create billing document with different document currency for more on proposal 2.
Keep us posted on how you are proceeding with the solution.
Please keep us posted with how you are proceeding on the solution.

Intercompany Billing - Destination country

Hi,
The scenario is: There is a Sales order from FR to UK to deliver goods.
In the intercompany billing document --> Header --> Tax --> Destination country, i would expect 'FR'.
But, the system is still considering the Destination country from the Ship-to (RE).
May i know if i am missing something here.
thanks & regds
Narain

Hi
I think there is a small confusion between Intercomany billing and Export sales.
Your case is intercompany billing and it need not be always export.
As your SH is from FR the destination country will be FR only and this is correct, the only difference is that the delivery is done from a plant from a different company code. The delivering company code can be either from the same country or from different country. This is the intercompany scenario.
An export sale need not be intercompany. The SH will be from different country and the selling and delivering company codes can be same. In this case, the destination country will be UK.
I think this makes things clear.

Intercompany billing has 2 line items referring to the same salesorder item

Hi All,
I am posting Intercompany billing documents using Idocs. I am using the standard function module that creates INVOICE IDocs, but these Idocs are failing with error text "Document contains same order item more that once".
The problem lies here, the PO that is been used is a STO (Scheduling Agreement) and the inter company billing the line item has the same material repeated twice but change in the quantity field. So, when I am posting document using Idocs we come across a segment E1EDP01 which has your quantity, weight, line item number and other fields. This segment is getting repeated twice with two different outbound deliveries.
So, I think the solution is a mixture of both functional and technical....
So, what I am planning to do here is for this particular material when ever it comes across duplicate entries add all the quantities fields and other numerical fields in the user exit and then refresh the internal table and then enter new entries. This could be done, but I don't know what could be the functional implications if these changes are made.
Request you all to let me know what exactly needs to done in order to avoid these scenarios.
Raghuram.

Hi Raghuram,
I found a very important SAP Note 103051, details are below.
An IDoc processed by function module IDOC_INPUT_INVOIC_MM (of category INVOIC01) must not refer to the same purchase order item in several invoice items. This is also valid if for a goods receipt-related invoice verification several delivery notes belong to the same purchase order item.
Depending on the system settings and the situation, various error messages can occur (for example, FD240 'Order item ... selected more than once' or M8050 'Balance not zero: & debits: & credits: &').
In this situation module IDOC_INPUT_INVOIC_MRM generates error message M8321 'Document contains same order item more than once'.
For example, this situation occurs if you work with individual batch valuation and the SD billing document executes a batch split for different batches which belong to the same purchase order item and delivery.
Other terms
INVOIC, SAPLIEDI, M8047, M8, 321
Reason and Prerequisites
This is because of the program design.
Solution
There is no solution for IDOC_INPUT_INVOIC_MM.
Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active.
Owing to this symptom, billing documents for single batch valuation with batch split cannot be settled in MM-EDI inbound processing. The settlement generates exactly the situation described (several invoice items for the same purchase order item). In this case, the only solution is to deactivate the billing of the batch sub-items in SD Customizing and to calculate the main item only.
Hope this helps.
Reward if helpful.
Thanks

Third party n intercompany billing

Dear All
Is Third Party and intercompany billing is same.
Thanks in Advance
Annie

No. Both are two separate process.
Incase of Inter-Company Billing, the same group company is being billed, where as in case of third party billing, our company bills an external customer. Configurration & process for both are very different.
For additional information on the same, please refer to link below:
Link: http://help.sap.com/
Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on ...........
Additionally, Third Party Scenario can be configured in two ways:
1. Third Party with Shipping Notification
2. Third Party without Shipping Notification.
Similarly, Even Inter-company scenario can be mapped differently.
You can get good information from help.sap.com
Regards,
Rajesh Banka
Reward points if helpful.

Different currecny in intercompany billing

Similar Messages

Maybe you are looking for