Intercompany Billing using RD04 Output

Hi,
We are using RD04 successfully to post incoming AP invoices. We have the timing for RD04 set to '4'.
However, we have a problem when the original invoice is not released to accounting if there is some error. In this case we don't want the system to process the RD04 output.
In other words, I would really like it if someone could let me know how I can make 'successful release to accounting' (VBRK-RFBSK=C) a pre-requisite to processing RD04.
Thanks,
Anisha

Hi Anisha,
Go to V/40 (Output types for Billing)
Select your output type RD04 and check the Access sequence assigned to it.
It might be "0004". Copy this access sequence into "Z004" access sequence and in this Z004 access enter the requirement as "62". This requirement routine will validate the entire billing document and also verify whether the data has been passed to accounting.
             Assign the new Access sequence to your output type.
          I don't recommend you to change the RD04, Its better to copy the RD04 into custom output type like "ZD04" and assign the access sequence to it.
Now new output will be triggered only after the billing document was save properly and data been passed to accounting.
Hope this gives you clear idea.
Regards,
Ajai.
Don't forget to reward points if helpful.
null

Similar Messages

Intercompany billing - using condition type PI01 = VPRS

In the intercompany billing we are going to configure the condition type PI01 to copy the amount in the condition type VPRS in the order. Can anyone give me a proposal of how to do this?

Hi,
Check copy controls from Delivery to blling document - VTFL is there any thing missing Header as well as item level, at what lelvel your determining the price. pricing at main item level or batch level.
Pricing should be at main item level
There will be two items 1 is main item 2. is Batch item
chek cumulate cost has checked on main item or not
and also gothrough the related Notes:
Regards,
MH

Intercompany billing RD04 with goods-receipt-based invoice verification

Hi members,
we think about making use of the automated intercompany billing functionality with the RD04.
In our logistic processes we apply the goods-receipt-based invoice verification. This is a very important requirement. That means that invoices can be only posted if the goods receipt has taken place.
Is there a possibility to configure the automated intercompany billing so that this requirement is met?
Any ideas? Any documents? Helpful links?
Thank`s in advance.
Best regards.

Hi Imer,
I believe you must be following any one of below process steps for Inter company Billing:
Sales Order
Delivery
Customer Invoice
Inter-company Invoice
Or
Inter company STO
Delivery
Invoice
GR Based on Inter Company STO
Automatic Vendor Posting (RD04)
If you are following first process then no need for GR at all.
If it is second process then assign Requirement Routine (Logic: Check GR has been completed or not for STO, if completed Pass the requirement else fail. take MM consultant's help for exact table and field details if needed.)
Change the RD04 trigger based on Background Job processing and Run Background job for processing of the Output type.
Regards,
MJ.

Tax conversion during Intercompany EDI (RD04 output)

We have a situation where there is an intercompany billing from company A to B - both of them are in different countries and hence follow different tax codes.   The RD04 output posts the AP document in company code B with a different tax code.    We have checked OBCD, and this does not carry any relevent config.    What else governs this conversion ?
Many thanks,
Sanker

Hi E_Hinojos and all,
I went to CUNI again and under ALE/EDI, the field was already populated with EA. The solution was that I just need to check the "Primary" box under that field and the error message went away.
Now, I'm getting a new error message after simulating the IDOC again in WE19:
IDoc number            0000000000198023
Direction              2     Inbound
Status                 51    Application document not posted
G/L account 191100 requires a valid tax code
Message no. FS214
Diagnosis
The master record of account 191100 requires you to enter a valid tax code in each item for this account in company code 0001.
System Response
Error message
Procedure
Enter a valid tax code.
I've already maintain transaction OBCD with input tax codes but I'm not sure whether I did it correctly. I'd like to know how the system would know which tax code to take or choose from OBCD table? The GL 191100 under transaction FS00 allows input tax codes only.
Any suggestion would be appreciated.
Thanks.
Edited by: Steven Khoo on Feb 18, 2011 4:16 PM
Edited by: Steven Khoo on Feb 18, 2011 5:17 PM
Edited by: Steven Khoo on Feb 19, 2011 12:45 AM

In VF01, before saving the billing document, can we use "issue output to"

In VF01 transaction before saving the billing document, can we use "issue output to" under Billing Document in Menu.
i.e., can we enable the option "Billing Document -> Issue output to -> Issue output to"

Hi,
No as a standard, unless the billing document is created and released to accounting, you can't use issue output to.
Regards,

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

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 codes 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

Order Related Intercompany Billing - Third Party Order

Dear all,
I have configured intercompany billing that is based on the delivery and i have done that successfully, then I tried the third party process but after billing the third party order then the intercompany billing doesn't show up in the vf04, I have searched the SAP Notes especially SAP Notes 63459 but I really haven't got the clue how to do that clearly, if somebody can help me how to configure the intercompany billing for my requirement. I'm using SAP 5.0. I believe something missing in the copying control between sales document and billing document and also for the output type.Please help me very urgent.

hi,
Customizing settings are reported in notes 338922, 109254 and 308989.
During delivery creation the LIKP fields VKOIV/VTWIV/SPAIV/FKAIV/PIOIV/FKDIV/KUNIV must be filled in program FV50XFLK_LIKP_FUELLEN_IV_UML. If you checkt this table and not all of these fields are filled, you have the wrong the customizing. If the error is in your pruduction there is a report with which you can correct the relevant deliveries (of course after correcting your customizing): see note 176476.
Balazs

Intercompany billing issue

Dear Experts,
Intercompany billing between 2 company codes(existing under same company) in system. Let say, company 1100 is a customer to company 1600. Currently, when we create a billing in SD module (VF01) and posting to FI/CO, AR document will be created for Customer 1100 in company 1600. User for company code 1100 have to do manual entry for that incoming invoice in AP.
Our requirement is , when we create billing and posted to FI, system have to create accounting document (AR) for company 1600 and AP document in company 1100 automatically for the same item and amount.
Would appreciate if you could provide some suggestion on this requirement.
Regards,
N.C.Reddy

Hi,
It available in standard inter company scenario
Configure Automatic vendor account posting in
IMG >> SD >> Basic function >> Billing >> Inter company billing
Use out put type RD04
Which will create IDOC document and post invoice verification
http://wiki.sdn.sap.com/wiki/display/ERPLO/Inter-CompanyBilling-AutomaticPostingToVendorAccount%28SAP-EDI%29
Kapil

Details for ALE Message type 'INVOICE' for intercompany billing ?

Hi all,
I have a requirement that i have to create the Invoice receipt for FI when the billing document is created ( VF01) in the same client?
Please provide me the details for this
such as output type , process code and other master data settings that have to fill?
Thanks,
Vamshi.

Hi prakash,
Thanks for the reply and it is very helpful.
But i am using message type RD00 and shall i use this?
Else, please specify the details that i have to maintain to use RD04 clearly stap-by-step?
Thanks,
Vamshi.

Recognize COGS in intercompany billing process

Dear expert,
I read the intercompany billing process and have some confuse.
The process like that: CC1(company code 1) sells to end customer, CC2 (conpany code 2) (internal relationship) issues good.
1, CC1 sells to end customer. CC1 create the SO
2, CC2 creates the DO and PGI, that recognize the COGS at CC2 for the internal sales.
3. CC1 creates the billing to end customer --> record the revenue of CC1
4. CC2 creates the internal billing to CC1 --> record the internal revenue of CC2
My question is, follow this process, I don't see the COGS of CC1, there is only a outbound delivery create by CC2 and COGS of CC2.
I read the document about cross transaction, but it guide me only for steps above.
Are there any mistake here?
Please give me a help.
Thank you in advance!
HongDM

Dear expert,
I have some question about the document flow of the intercompany billing process.
Company code 1 (CC1) sell to customer
CC2 issue goods to customer of CC1, then internal billing to CC1.
the step as below:
1. CC1 create SO (sell to customer)
2. CC2 create outbound delivery to Customer of CC1, recognize COGS of CC2
3. CC1 bill to customer, recognize revenue of CC1
4. CC2 create internal invoice to CC1, recognize revenue of CC2
in internal invoice of CC2, update the output RD04. Does it recognize COGS and goods receipt to CC1? Because as above document flow, I see that, the CC1 don't have COGS, not receipt goods to plant of CC1 and Account Payable for CC2. There my thinking as logic of flow, but I'm not sure what the EDI and RD04 can do. Can you tell me about that.
Thank you very much, this is very helpful for me.
Best regard,
HongDM

Order-related intercompany BIlling - RVIVAUFT

Dear SAP Experts,
Currently I am doing the Order-related intercompany Billing, However the 2nd billing document is not created. I have referred to OSS notes and they are referring to report RVIVAUFT and the output type RDIV and copy control settings.
I have made the copy control settings (Order Billing - Requirement 036 in the Item cat.) and I could not find the output type RDIV (Billing outputs). I am using ECC6.0
- Can anybody tell me how to use this report RVIVAUFT, which billing documents I have give in the selection screen?
- What is the standard output type i can copy to create RDIV?
- Is there any additional configuration I need to do for Order-related intercompany Billing?
Regards,
Murali

Hello Raghavendra,
I have already implemented the notes you have referred, however the process is not working.
Let me tell you my requirement in detail:-
We have two company codes one in India (Comp 1) and second in Germany(Comp 2) who provides the service to their customers.
Scenario:-
The German Company sells the Service to customers in Germany, however the service is done from India remotely. Once the service is done German company will create an Invoice to customer and Indian company will invoice the German company
Customizing:-
- I have made all the settings for the Intercompany Sales (Delivery related Intercompany)
- Customized according to the notes 381042.
Master Data:-
- Extended the Material to Germany company
- Maintained the Intercompany pricing conditions.
- Condition record for RDIV is maintained
Transactions:-
1. Customer order is created in German Company (VA01)
2. Customer Invoice is created in German Company (VF01)
3. Execute the report RVIVAUFT to create the Invoice to Germany Company. (SE38)
So When I execute the report RVIVAUFT, system is giving a message Material is not maintained.
Can you please let me know whether I am following the right steps in the system?
Regards,
Murali

Free goods in intercompany billing

Hi,
I customize free goods functionality in SAP and all seems to be all right. A sales order makes a delivery with the two itens and after that the invoice have two itens one of then with condition TANN. Everything is perfect...
But may question is: how can i do this in intercompany billing once in this kind of billing i haven´t the sales order but a purchase order?
Best Regards
João Fernandes

Free goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
This is the Limitation of setting up free goods
Cheers

List the intercompany billing numbers from sale order numbers.

suppose i have a set of sale order numbers. is there any report can list the intercompany billing numbers related to those sale order numbers? i don't want to use VA03 because it can display only one sale order number.
thank you very much,
Anek

Hi Anek,
Run the transaction code VA05. Click on the Further Selection Criteria, Select the check box 'Sales Document Type' and click OK. System will ask for the Sale Document Type. ENter the inter company Document Type, Press Enter and select the date range press Enter.
System will list the orders.
Hope it helps. Let me know whether it resolves you issue.
Thanks & Regards,
Nagaraj Kalbavi

Automate creation of Intercompany billing document

Hello All,
We have a requirement to automate the intercompany billing document to be created whenever F2 billing document is created ( without using VF04).
Any input regarding this will be greatly appreciated.
Thanks,
Nagaraju

After goods issue has taken place, you can process the delivery for billing. You can create the billing documents just like any other billing document on the Billing screen:
for a single billing document with the menu path Billing document ---Create.
for several billing documents with the menu path Billing document -
Billing due list.
The delivery may have to be processed for billing twice.
The delivering plant processes the delivery to create an intercompany billing document (billing document type IV) for the selling company. This company code posts invoice entry for this billing document.
The billing document is automatically billed to the internal payer that is assigned to the sales organization. The intercompany charges that appear in the intercompany billing
document represent the actual amount that the delivering plant is charging the sales organization.
If the selling company is selling the goods to a customer, it processes the delivery to create an invoice for this customer. The system can take the prices from the order or determine new prices. It takes the quantity to be invoiced from the delivery.
The billing due list for the intercompany invoice is generated after the customer invoice has been created.

Intercompany Billing using RD04 Output

Similar Messages

Maybe you are looking for