Intercompany Billing without MM module

Hello Guys,
I'm implementing ECC6 and we would like to have a simple Intercompany Flow in which: for each SD invoice made in company A to customer "company B", account payable FI postings are automatically triggered in company B for vendor "company A". We do not have MM, so we need direct FI postings to AP.
Have you ever seen it working ? Do you guys have any documentation on this subject or any customizing guidelines ? I get the basic idea (idocs, etc) but need more guidance. Thank you !

Create 'Company B' as a customer in Company code A.(t-code FD01)
To indicate that this is an inter company customer for Company code A, maintain the Trading partner field in the control data of the customer master i.e 'Company B'. Here you give the Company ID of the Company code B.
Similarly the vice versa i.e (create company A as a vendor in company code B + give the trading partner for vendor company A as the Company ID of company A.)
Maintain 'Prepare Cross-company code transactions". Transaction OBYA for both company codes.
The rest would be covered by regular transactions. Like the regular payment program would pick up any due and make payments.

Similar Messages

Intercompany billing without many companies

Hi,
Is it possible to define intercompany billing without defining many Companies?
How would that be done?
We have a client request where they want intercompany billing within parts of their company. This for sure could be solved by defining many companies but that also would make things very complicated.
At another client the intercompany flow is handled through CO but this is not applicable at this client.
If anyone understand my question I really appreciate any feedback.
Best regards
Mattias

Create 'Company B' as a customer in Company code A.(t-code FD01)
To indicate that this is an inter company customer for Company code A, maintain the Trading partner field in the control data of the customer master i.e 'Company B'. Here you give the Company ID of the Company code B.
Similarly the vice versa i.e (create company A as a vendor in company code B + give the trading partner for vendor company A as the Company ID of company A.)
Maintain 'Prepare Cross-company code transactions". Transaction OBYA for both company codes.
The rest would be covered by regular transactions. Like the regular payment program would pick up any due and make payments.

Create Intercompany billing without Good Issue

Hi Gurus,
I use Cross Company purchasing process with One step configuration. Normally it's used to be like this:
1. Create Outbound delivery with reference to PO (t.code VL10B)
2. Post good Issue --> automatic generate GI & Good Reciept document
3. Create Intercompany billing with reference to the Delivery above.
But now I want to go directly from step 1 to step 3 that means I want to create Inter. Billing with reference to Delivery which has not been post Good Issue. What should I do to solve this problem?
Thank you very much,
Hong Trinh

Hi,
You need to initially decide if you want to go with Cross company STO process through Purchasing or Intercompany Sales/Billing through Sales.
Directly going from step 1 -3 is not possible.
Only after you do a GI from the replenishment delivery and GR at the receiving plant will you be able to create an Invoice.
If you are going with the Intercompany billing process, the sold to party/ship to party in your delivery should be the internal customer/plant and not the external customer. In this case you first need to create a F2 invoice and then IV invoice.
Regards,
Amit

Cross company sales without intercompany billing

Hello,
We are trying to set up cross-company sales without intercompany billing. Here is our scenario:
Company code 1000, Sales area 1000
Company code 2000, Sales area 2000
Sales order is entered in sales area 2000, but is delivering from a plant in company code 1000 directly to sales area 2000's customer.
We would like this scenario to work similarly to the "stock transport order without intercompany billing" scenario, where intercompany billing is not used; rather, the intercompany clearing accounts defined in FI are used.
We have removed the intercompany billing type defined in the SD config, which has prevented the system from creating an intercompany billing document. However, the accounting entries are not correct.
The problem is with the post goods issue. The inventory is being relieved into company code 1000's cost of goods sold. Instead, we want it go to the cost of goods sold in company code 2000.
From a financial perspective, it is currently doing:
Company code 1000:
Credit Inventory
Debit Cost of goods sold
But we want it to do:
Company code 1000:
Credit inventory
Debit Intercompany A/R clearing account
Company code 2000:
Credit Intercompany A/P clearing account
Debit Cost of goods sold
Does anybody know how to configure this?
Thanks,
JB
Edited by: Jimmy Brush on Aug 19, 2010 11:13 PM

Hi,
Check these notes:
SAP Note 109254 - Customizing stock transport order Cross Company
SAP Note 338922 - Analysis note for cross-company transactions (delivery)
SAP Note 543821 - FAQ: cross-company processing
Regards
Eduardo

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.

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

Intercompany Billing Credit & Debit Note

Dear All,
I have configured intercompany billing. Now i can able to create invoice for Supplying part to Ordering Party. This invoice creation without sales order na. So, if i want to create credit & Debite memo for supplying party to Ordering party how to create. Because here we are creating invoice wioth out sales order and creating with reference of delivery note. In this process sales order creation belongs to ordering party to customer. So where we can maintain Credit & Debit note for Supplying party to ordering party. I think when we create invoice can we maintain billing type as credit note? please suggest me to maintain Cr. & Dr Memo In Intercompany billing between Supplying company to Ordering company.
Thanks & Regards,
Anj

Hithere,
For intercompany stock transfer if you want to implement credit & debit memo in intercompany you need to reference credit & debit memo requests CR & DR or the returns order with delivery NL. You will define them in the sales area of the supplying plant. Then you maintain the copy controls from RE to G2 / D2 or CR / DR to G2 / D2.
For intercompany sales, the customer returns the goods to the ordering plant. Not the supplying plant. Coz customer doesnot know from where the ordering plant brought the goods from. So in that case customer to ordering plant is standard returns process. Returns between the ordering & supplying plant is again like mentioned above.
Regards,
Sivanand

Give me the Configuration steps for intercompany billing and third party s

Hi Gurus,
Give me the Configuration steps for intercompany billing and third party sales and give me a brief description with examples.
Regards,
YSR

Dear YSR
Check the links
[Cross Company Configuration|http://help.sap.com/bp_bblibrary/500/Documentation/J62_BB_ConfigGuide_EN_DE.doc]
[Third Party Without Shipping Notification|http://help.sap.com/bestpractices/BBLibrary/html/J55_ThirdPartyWOSN_EN_US.htm]
Third party order processing is as follows:
Assume three companies X, Y and Z
X - The company,
y - The customer
Z - Vendor
When ever X gets a PO from Y to supply some goods, X has an option of either manufacturing those goods or procuring those goods.
If he is procuring the goods, there are two methods that are generally followed:
Method 1)
After receiving the PO from Y, X creates a sales order against Y.
Now at the same time he also creates a PO to a vendor Z to produce the goods
Z produces the goods and supplies to X
X receives the goods from Z
Then X delivers the same goods to Y.
After that X invoices Y and Z invoices X.
Note : Here there is no direct/ Indirect relation between Z and Y.
This process is known as Trading Process. and the Material here is created with Material type HAWA.
The other method is a Third party order processing method:
Here the glaring difference is that instead of Z supplying the material to X and X in turn supplying the same material to Y.
X authorizes Z to supply the material to Y on his behalf and notify him once the delivery is complete.
Now Z supplies the material to Y and acknowledges the same to X.
Z will send a copy of delivery acknowledgement and invoice to X.
After receiving the delivery confirmation and invoice from Z, X has to verify the invoice and this process is known as invoice verification and is done in SAP through Tcode MIRO.
The next step for X is to create an invoice and submit to Y
Only after the invoice verification document is posted then only X can create an invoice for Y.
This is the business flow that is followed for third party order configuration.
There are few steps that have to be configured to enable the system to function as mentioned above.
Step1)
If you are always followwing a third party process for a material then you have to create the material using item category group BANS.
The procument type should be marked as External procurement (F) in MRP 2 view of the material master record.
if you are not always allowing third party order processing then u can create a material master record with item category group as NORM and the procurement type should be marked as ( X) meaning both types of procurment ( in house manufacturing and external procurement).
Step 2)
the item category in the order should be manually changed as TAS.
For that you need to confugure the item category determination
ord type + item cat grp + usge + Hiv level = Item cat + Manual item cat
OR + NORM + + = TAN . + TAS
OR + BANS + + = TAS
Step 3)
make sure that during the item category configuration for TAS you need to mark relevnat for billing indicator as F
Step 4)
The schedule line cateogry for this type should be CS.
make sure that you mark subsequent type as NB - purchase requisition in this schedule line category as this will trigger the purchase requision order immediately after the creation of the sales order and the PO to vendor is created against this purchase requiesion.
thanks
G. Lakshmipathi

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 for multiple Profit centers

Dear All,
We have a situation to do intercompany (company a to company b) billing without extending material. Also, maintain one plant to maintain stocks that is in company a. Customer place the order in company b system will do billing without maintaining any stocks in company b so our requirement is to generate profit centre wise P/Ll for company a & company b.
Any suggestion to overcome this scenario ?
Regards,
Madhawa

Thanks for your interest.
The requirement is based on the following objectives:
1) Reductiion in the number of plants
2) This is required coz a stock may be lying at a particular location (plant) which can serve as a common stock for all Business units (Profit Centers). Since it is in the same plant, there will be no requirement for stock trf. (goods issue & goods receipt) But then it should facilitate assignment of the profit centers. I strongly believe that could be easily dealt with sales order related production (MTO) through substitution rules but I have doubts about MTS coz i cant find any substitution rules configs.
I hope it clarifies the requirement

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

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 vf01 error no accounting document generated

Hi,
I face the problem while saving intercompany billing VF01 warning message no accounting document generated,
when I manually realise biling VF02 it posted without giving any error message.
I also check billing doc. type VOFA I doesnt check posting block field.
Pls suggest what may be the reason.
Thanks & Regards
Ashish

Dear Friend,
To resolve the error, you can analyze Account determination in the billing document. Process:
Goto T.Code: VF02 & Enter Invoice number
Next (On the top most strip) goto Environment
Next (Select Environment) go to Account determination
Next (In Account Determination) select Revenue Account Determination (first option)
This will list all the condition types in the Billing document & analyze each condition & check for which G/L accounts is not determined.
Possible errors:
1. VKOA not maintained for required combination
Solution: Maintain the combination in VKOA.
2. Account Assignment of Customer / material not maintained in Customer / Material Master (If maintained in combination in VKOA).
Solution:
Option 1 (Standard solution):
step 1: Cancel Billing Document --> Reverse PGI --> cancel Delivery --> Cancel Sales Order
step 2: Maintain Customer master / Material Master correctly.
step 3: Recreate sales Order --> Delivery --> PGI --> Invoicing.
Option 2:
Force the Account Assignment Group of Customer / Material through Debug in change mode of Billing document, which will release Billing Document to Accounting.
3. Account Key not maintained in Pricing Procedure:
Impact: This may create accounting document, but if condition type, which are to be posted to account, but do not have account key maintained in pricing procedure, it will not be post the relevant condition type to G/L account.
Regards
AJIT K SINGH

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 without MM module

Similar Messages

Maybe you are looking for