Intercompany billing -accounting process
Hi,
I would like to know the best way of accounting the intercompany transactions.
From my understanding, intercompany billing transactions accounting should be handled as below;
1. in Provider OU, debit cost to provider's P&L a/c when cost is incurred
2. While generating receivable invoice, credit revenue to Provider's P&L a/c.
3. this way, The profit margin (if margin is charged over the cost by provider OU) reached to provider P&L a/c. (Net effect between cost and revenue)
4. In receiver OU, debit cost to P&L a/c and create liability for payment while AP invoice is generated
5. Settle provider and receiver a/c by cash payment/receipt throgh receivable/payable invoice.
somebody please validate my understanding, or please suggest any other possible way of doing this.
Thanks
Mukesh
Hi
You are right with your understanding
Dina
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 DuttaCheck 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.
-
Accounting entries for intercompany billing process
hi,
can any body explain what it intercompany billing process and intra company billing process and STO processess.
and their individual accounting entries of these three business with excise impact.
regards,
balajia> Total Questions: 494 (232 unresolved)
Perhaps you should reconsider the quality of your questions? In this one you seem to have put in absolutely no effort of your own, but I will put some effort into tracking down your next question for you...
Please read the forum rules before continuing further. -
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
AshishDear 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 -
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!
HongDMDear 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 -
Intercompany billing (sales) not reflecting in sales account 410001
Hi,
I need some clarification regarding intercompany sales process.
My client is having two company code named 8500 & 8700.
we have to sell 8700 material eg 870000 through 8500 plant 8501. For this requirement i configured intercompany sales.
i have assigned my deliverung plant 8501 and distribution channel to 8700 . Created Internal customer representing 8700 in 8500/01/01 sales area and assigned to 8700 sales organisation. Ordertype OR assigned to billing type IV.
I created a sales order from sales area 8700/01/01 with a customer 1920 and the dispatch plant is 8501.
I did delivery , PGI and i did normal invoice from 8700 company code to 1920 customer . sales account is reflected in company code 8700 ( g/l account 410001 in FS10N)
then i did intercompany billing from 8500 to internal customer. accounting document is generated. But i can,t see it in 8500 company code under G/L account 410001 eventhough it has created with accounting document in 410001.
Please tell me where this account is moving
Edited by: Mohamed.Naseem on Jun 22, 2010 12:53 PM
Edited by: Mohamed.Naseem on Jun 22, 2010 12:54 PM
Edited by: Mohamed.Naseem on Jun 22, 2010 12:54 PMSo Mohamed, So it is posting to right account and you can see the Accounting document. But when you display the account balances, you don't see the Accounting Document there? Is that the issue?
What T code are you using to display the account balances? Also describe briefly what you are doing after entering the transaction? -
Account determination error during intercompany billing invoice
Hi experts,
I am getting 'Account Determination Error' shows in red during 'intercompany' billing.
I tried to release to accounting but didn't help.
Pls advise
Br,
UmeshHi Sushant,
The error during the invoice creation. This document is for intercompany billing.
I checked in Account Determination Analysis --> Revenue Accounts
When I click on the Item no., it shows as 'No G/L account found in KOFI' & messege 121.
In VKOA, there are few tables but I am not sure how & what to compare between these two.
Br,
Umesh -
Account assignment order-related intercompany billing (SD-EDI-OM-IV)
Hello!
Intercompany billing is being generated and posted and intercompany accounts payable (IC AP) document is parked through IDOC and when trying to post this IC AP in the receiving company code is giving an error:
"Account 30069520 requires an assignment to a CO object
Message no. KI235"
CO object is missing because COPA values are not following into this IC AP document. Several SAP Notes have been installed, unfortunately without any help:
607799 - Posting to vendor account w intercompany billing before F2
916973 - Incorr partner PC in intercompany billing before ext billing
1766604 - INVOIC: IDoc w/ incorr account assignment for down payment
Currently we are trying to modify user exit V05NZZEN mentioned in SAP Note 607799 to be able to copy account assignment objects into the IDOC and IC AP document. SAP incidents have already been created and no help from SAP side due to some cases intercompany invoice is to be created before end customer invoice which is against SAP standard. There is also billing block and billing plan activated to the SD document types in the SAP system which are outscoped in SAP Note 607799.
Have anyone done modification to user exit V05NZZEN which would solve KI235 error?
Is there anything else which could be tried solve KI235 error?It seems couple of segments are missing in your IDOC settings. Have a look at the following notes:-
Note 328569 - INVOIC: segment missing in FI invoice; KI235
Note 1881464 - Error KI235 when post IDOC coming from SD billing output
G. Lakshmipathi -
CIN Pricing Procedure for Intercompany Billing Process
Hello All,
Please suggest me what Pricing procedure I can use for Intercompany Billing for CIN.
I have created a ZPricing Procedure coping the JINFAC but its for normal sales what CIN configuration I have to do for Intercompany billing.
Please suggest..
Regards
VenkatNot Answered
-
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,
SagarHi
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 & 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 -
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
thanksHi 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; sequence of invoices
Hello,
How can I block the IV/IG invoices before the posting to vendor account for the ordering company. We are using EDI to carry out the vendor account posting. Is it the copy requirement? How can check the FI posting from the routine?
Thanks
saptorI have created a copy req for VTFL (F2/LF) to check VBFA for an intercompany billing but it is not completely correct. When the Idoc is not processed successfully, the F2 invoice can be created before IV which is wrong. I normally have to check the FI posting in buying company code. How can I do this?
-
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 PMHi,
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
Maybe you are looking for
-
Create a "New Zone" in the "Forward Lookup Zone"
I am working I Windows Server 2008 R2 SP1. I went to DNS Server and tried to create a "New Zone" in the "Forward Lookup Zone" under "subdomain.domain.com". I got the error: "Zone Not Loaded by DNS Server". Tried to F5 to Refresh but still same erro
-
Can't see anything in ESB Control
Hi! I can't see any systems in ESB Control (no DefaultSystem, and no BPELSystem, Fulfillment or OrderBooking after succesfully deploying soademo_101310_prod). (There are some JavaScript errors too: URLObject is not defined) (WinXP, SOA Suite 10.1.3.1
-
Not seeing hosts or services in Bonjour
Bonjour "just works," except when it doesn't. When I started to wonder why I could only intermittently see my wife's MacBook in iChat and never via the Finder, I started looking for Bonjour problems on both computers. I couldn't find any, but eventua
-
Equalizer problem after lollipop update
Hi. I just noticed that equalizer is only working with walkman app. It worked just fine in kitkat.
-
Unique Problem, Need someone smart
I connected my iPod shuffle to my Xbox, and my Xbox formattted it and put new firmware on it, making it useless on Windows. I tried restoring it via the newest iPod updater, but it says "iPod service error." iPod service.exe is NOT on task manager's