Multiple Level Intercompany Billing - CRM

Hi,
I have seen mention of Multiple level Intercompany Billing in CRM.
Can anybody point me to some decent documentation on this, or provide an explanation of what it encompasses above R3 ? Some tips on how to set it up would also be great. The requirement is to chain various intercompany invoices in addition to the customer invoice when there is a shipment/sale between countries.
Thanks,
Steve Parnell

Hi Steve,
Multi Level Intercompany Billing is available as of CRM 5.0
You find an introduction here:
[SAP Help Portal -> CRM 5.0 -> (Multi)Intercompany Billing|http://help.sap.com/saphelp_crm50/helpdata/en/f0/3b6b3de666930fe10000000a114084/frameset.htm]
In R/3 there is Intercompany Billing but no Multi Level Intercompany Billing supported.
Regards
Ralf

Similar Messages

Incoterms in Intercompany Billing Document

My Dear SAP Mentors,
Can you please let me know that from where in "Purchase Order" incoterm appears at item level...
In the concerned PO at Header level there is a seperate incoterm for e.g. DDP Jyderup...I know this comes from the vendor master record.
There are two items in the concerned PO...
I am confused as when I go to item details Delivery tab then for one Material say 212244 incoterm comes as DDU gebze and for another Material say 253264 incoterm comes as EXW Poland.
1) Any idea from where this is coming...?
2) Which incoterm should appear at the intercompany billing document ?
3) Is it correct to have a incoterm from customer master record (Ship to party) in the intercompany billing document.
4) Else please let me know the standard setup or incoterm get affected by copy control in documents.
Requesting you all to kindly help me on above queries...
Best answers would be appreciated by full points...
Thank You !
Best Regards,
Anubhav

Hi,
1) Any idea from where this is coming...?
- This could be from Info record. Use T.code ME12 to check the inco term for the particular vendor + material combinations. You can view the details under Purchase organization data1.
2) Which incoterm should appear at the intercompany billing document ?
- Ship-to party inco term.
3) Is it correct to have a incoterm from customer master record (Ship to party) in the intercompany billing document.
- This is correct
Regards,

Pricing error in intercompany billing

My client is using the intercompany billing process.
There is a BOM item with item category group LUMF and the pricing happens at sub item level. In the sales order and the customer billing document the pricing happens at sub item level only.
But in the intercompany billing the pricing happens at both main item and sub item levels. The pricing procedure is dfferent here.
Both the sales pricing procedure and intercompany pricing procedure has the condition type ZI11. The requirement 22 is attached to the condition type at both the pricing procedures.
In the intercompany pricing procedure, subtotal L is assigned to the condition type ZI11.
The condition type ZI11 is configured as under.
Access Seq : ZI11
Condition class : B (Prices)
Cond category : C (Qty)
Rounding rule : commercial
Manual Entries : B (Automatic entry has priority)
Item condition
Amount / percent
Int-comp Billcond
Can anyone tell me why the item is priced at both main & sub item level in the intercompany billing.
Regards,
Bala

Hi,
Please check with the defination of the Item cateogry for the Main Item for the InterCompany Invoice.
The relevance for pricing should be ticked off.
Reward points if it helps.
Regards,
Harsh

Intercompany billing exchange rate is not updated on change of the currency

Hi,
I create a intercompany billing via VF01 with reference to a outbound delivery, and the currency is picking up from the customer master which is USD. But I need to change the currency to be the same as the PO which is GBP. So I change the currency field from USD to GBP in VF01 (both header and item level), the exchange rate field remain unchanged and still showing the USD rate instead, and the price is wrong.
Anyone know what happend to this? Appreciate your advice.
Thanks,
YH

Hi Damu,
Once you change the header currency, line item currency will be changed also.
My problem is even I've change the currency to let say GBP, the exchange rate shown in the billing document is still in USD rate, but NOT in GBP rate.

Issue with Intercompany billing- Third Party

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

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

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

PO pricing to be copied in Intercompany Billing

Hi,
In STO process the requirement is that in intercompany billing documnet the the pricing should be copied from the PO.
I tried in VTFL - Item - then Price Source ans select' A' -PO. But it did't work.
Can anyone suggest how to solve the issue?
Regards
Jyoti

Hi,
Check the pricing type field in copy control at item level. Also check that the appropriate pricing conditions are included in your pricing procedure and make sure that the right pricing procedure is determined in the billing document.
Hope this will help you to resolve the issue.
Thanks and regards,
Atul

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

Order related intercompany billing scenarios

Hi,
Need suggestion for order related intercompany billing from project. The scenarios is as follows.
There will be two diffenr company code under the controlling area of the project. Parent company will use resources from supplying company for executing the Order from customer. The project is service industry scenarios. The billing will be order related milestone billing. Milestone will be triggred from Project builder. There should be automatic revenue & cost posting to respective WBSE on doing billing to customer i.e. Revenue of supplying WBSE will become Cost to Parent WBSE.
I would like to request you to suggest on the above process for mapping into SD-PS
Thank you for your coopearation.
Regards,
Rakesh Pradhan

In Sale Order at Line item level, maintain the plant of supplying plant & not the one which have received order.
Ensure intercompany setting is in place.
Regards,
Rajesh Banka

Create Multiple Level in Marketing Organization

Dear All,
If I have a multiple positions under Marketing Organizations and I want to make a levels for them, how can I do that? i.e. if I have an employee who reports to the supervisor and this supervisor reports to the manager, how can I configure the levels for each one in case that the manager has the highest level and the employee has the least. This will help us to configure our CRM system so the manager can see all the leads which are assigned to the supervisor and the employee.
We have CRM 5.0 on windows server 2003 and SQL2005.
Regards,
Mai AlDabbagh

Hello Mai,
If i understood your question correctly, You cannot create multiple levels under positions in oranization structure. You can define various positions under each organization unit and then you can assign employees to corresponding positions.
what you are trying to achive is possible with partner functions are partner determination within lead management. you have to define a rule within your partner determination and then assign this partner determination procedure to lead transaction type.
by this you can configure such a way that manager can see all the leads which are assigned to the supervisor and the employee.
Thanks
Raja Pamireddy
CRM Marketing forum Moderator.

Intercompany Billing IV

Hi Gurus,
I have a scenario in which I created standard SO and then delivery, then Invoice. This is related to intercompany sales process and now if I would like to create intercompany invoice document, system is showing an error "item are not open in delivery document" .
If I look at document flow it does shows "being processed" for delivery document. I have checked all the configs and copy control is being maintained between delivery type & Billing type.
Kindly help me and let me know the clue on how to solve this isue.
Thanks in advance...
Bawa

Dear Bawa Bawa
I had the same error or problem when i first configured intercompany sales a year back but i solved on my own by configuring the process once again ( I am not able to recollect what was the wrong customization or wrong settings when i did first which subsequently i corrected it)
I am pasting here with a doc prepared by me on intercompany sales which you have to reconfigure
It is definately a small procedure mistake which you can correct
I hope this will help you
Company codes 1573 and 1574
Sales org     0003 (assigned to CC 1573) and 0009 (assigned to CC 1574)
Dist channel 04 (assigned to sales org 0003) and 09 (assigned to sales org 0009)
Div 00 in both setups that is in MMR it is maintained as 00
Plant   1002(assigned to CC 1573) and 1006(assigned to 1574)
Storage location1002     (in plant 1002) and 1006 (in plant 1006)
Material Balaram     Maintained in both the plants
Stock of balaram          nil (in plant 1002 ) and 50000000(in plant 1006)
Customer     70000099
Order entered in sales area   0003,04,00
In the order at item level go to shipping details and change the plant to 1006 and storage location 1006 as the automatic plant determination will be 1002
Pricing procedure is RVAA01(for customer)
Maintain the inter company price for the material condition type PI01 in VK11
Maintain the condition record   for condition type IV01 in vk11
Save the order
Create delivery
Create transfer order
Create normal F2 invoice for the customer
Now once again go to VF01 and choose inter company billing and give the delivery document and execute
Now an inter company billing is created with pricing procedure ICAA01
               NECESSARY CONFIGURATIONS
1.   Customer should exists in both company codes
2.   Material should exist in both the plants
3.   Stock should be maintained in the second plant in this case it is 1006
4.   Both the distribution chains should be properly assigned in Enterprise structure
      assignment in this case 0003,04 to plant1002 and 1006 and also 0009,09 to plant
      1006 and 1002
5.   Material should belong to same division
6.   Internal customer for inter company billing for sales org is to be defined for the
      respective sales org in Enterprise structure definition details for that respective sales
      org in this case it is for S.O 0003 it is 70000099
7.   In IMG- S.D BILLING- INTERCOMPANY BILLING All the three
      Necessary configurations for inter company billing has to be done
8.     In assigning organization units by plants for the plant in this case for the plant 1002 you have assign sales areas 0009,09,00 and for plant 1006 you have to give sales areas 0003.04,00
9    You should assign the order types that will trigger inter company sales
10   In the third assignment you have to give the customer created for that S.O same as
        Step5
11 Pricing procedure for sales for the customer is RVAA01 and assigned in T code
        OVKK for the combination of 0003,04,00,A,1
12     Pricing procedure for sales for the customer is ICAA01 and assigned in T code OVkk for the combination of 0003,04,00,I,1
   13     Condition records to be maintained in VK11 for condition types PI01 and IV01
Regards
Raja

Intercompany billing - Returns

Hello All,
I have a standard intercompany billing scenario: there are three companies A, B and C with different company codes. Company C orders goods at company B (order created at company B), whereas company B inputs supplying plant from company A, which ships directly to company C. Then we have internal billing (IV) between A and B) and normal billing F2 between B and C. This is OK.
Normal return process for this intercompany billing is also standard and OK.
What about when we have return first from C to B (I guess standard return process) and then from B to A (where A and B are on the the same SAP installation/system)??? I guess there cannot be standard return order (with reference to IV billing) with return delivery and credit memo from A to B, because we need goods issue and invoice receipt at B. We cannot have a STO with billing (as we need a reference to the original IV internal invoice).
Anybody can help me with this scenario? Any help will be highly appreciated.
Regards,
Smoczek23

Yes, we had tried that, and just to be sure I just re-tried it myself, changing the sales office at the header level of Sales order, but still nothing has changed against the Invoice. What we did not want to do was cancel all the documents back to the sales order and then re-create. We have about 500 document/items to be changed, so that would take simply ages.
Are we up a creek without a paddle do you think?.
Jas.

Intercompany Billing STO

Hi
I created a new delivery type (copied from NLCC) and new Billing type (copied from IV). When creating the billing document, by default it is creating F2 instead of IV. Let me know what else is missing?
How can I assign the Billing type to the inter-company delivery type?
Thanks,

Hi
How can I assign the Billing type to the inter-company delivery type?
That means that if you want to pick up new Billing type (copied from IV). for your new delivery type (copied from NLCC)
Go to OVLK and go to the details of your new delivery type
Here there will be a field called pseudo order type
Check what is maintained there? The standard should be DL or assign DL there
Now go to VOV8 and open up the details of DL
Here in the billing tab for intercompany billing maintain your new new Billing type (copied from IV)
Also make sure in VTFL between your delivery type and billing type the copy controls are maintained at header and item level
Now for you Zee delivery type your Zee billing type will be picked
Regards
Raja

Intercompany billing (SD) - LIKP-VKOIV + VTWIV + SPAIV are empty

Hi,
I am trying to create an intercompany billing at outbound delivery level.
Can someone tell me the function module where intercompany data is determined (LIKP-VKOIV, LIKP-VTWIV and LIPK-SPAIV) in VL01N transaction?
Thanks so much in advance!
Félix

Hi,
thanks for your reply,
Process flow is:
Create sales order
Outbound delivery
IV invoce from manufacturing plant to selling plant.
Invoice from selling plant to third party customer.
Settings are done as described in the various discussions:
1. Enterprise structure/ Assignment/ Sales and Distribution/Assign sales organization - distribution channel - plant: Done
2. Sales and distribution / Billing / Intercompany billing / Define order types for intercompany billing: Done
3. Sales and distribution / Billing / Intercompany billing / Assign organizational unists by plant: Done
4. Sales and distribution / Billing / Intercompany billing / Define internal customer number by sales organization: Done.
Master data has been created:
5. Internal Customer from selling plant has been extended to sales area from manufacturing plant.
6. Material has been extended to sales area and plant of manufacturing plant.
7. Pricing schme has been set up for manufacturing plant to invoice selling plant.
8. Prices have been set for manufacturing plant to invoice selling plant.
Sales order is created and delivery is created.
However LIKP-VKOIV + VTWIV + SPAIV are still empty.
Do you know a reason why?
When I worked with this 2 years ago I remember there was an standard coding (probably a function module) that was called at VL01N transaction to populate LIKP-VKOIV.
Would you know which function module this would be?
Thanks and regards

Multiple Level Intercompany Billing - CRM

Similar Messages

Maybe you are looking for