Actual Batch COst to charge intercompany billing

Dear SAP guru's,
We are having the scenario of intercompany where as we are charging the actual cost of product(SFG RM + FG PK) + tolling to intercompany transaction.to take the Actual cost we wants to go indiviual in SFG and FG process order and take the batch cost.Is there any report is their we can see :- process order FG ---> Process order SFG --- > Batch number FG -
> Batch number SFG -
> target qty of FG -
> Target qty of SFG -
> Target cost FG -
> Target cost SFG -
> Actual Yeild QTY FG -> Actual yeild qty SFG-- > Actual cost of FG -
> Actual cost of SFG -
> Variance in FG --- > Variance in SFG -
> date of creation.
Please give your valuable advice in details how could i get above mentioned report in SAP.
Pls help me out from this thanks in advance.
regards,
Vijay Pabale

Pabale
It seems to me that you are trying to cost a batch based on its raw materials.
In this case, I would suggest using tables AFPO, AFKO and RESB.
AFPO can tell you the Process Order that created the batch
AFKO can tell you the reservation number that this process order used
RESB can tell you the cost of each raw material, at the time of the reservation
With all three you can cost the raw materials of each process and then find the batch that each process created.
I do not know if this will help in terms of yields though. I also think you might need to be working with a Variable Cost type. But I think, this would be the easier path.
Hope this helps,
KhaledO.
(Egypt)

Similar Messages

Batch cost in billing

Hi all,
How can i make the cost (VPRS) in the bill to be the current cost of the batch.
Thanks

Hi,
These notes are useful:
SAP Note 1365939 - VPRS logic and Customizing settings in SD
SAP Note 547570 - FAQ: VPRS in pricing
If you have the problem in the transfer from SD conditions to CO-PA, check if you transfer only invoices to COPA, if you don't invoice the deliveries of free goods, then you don't transfer this 'sales' or costs of 'gifts' to COPA. You can check the customizing of COPA in tcode ORKE (IMG for COPA). SAP Note 74486 - INFO: Overview of consulting notes for CO-PA is a good summary about this issue.
I hope this helps you
Regards,
Eduardo
PD: I forgot SAP Note Number 33968 SD/CO-PA: Characteristics from sales doc tables
Edited by: E_Hinojosa on Sep 10, 2010 9:44 AM

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.

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

Intercompany billing - using condition type PI01 = VPRS

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

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

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

Need the exact difference betwn Intercompany Billing and Inter-project bill

Hi,
Can any one tell me the exact difference between the intercompany Billing and inter-project billing?
The decision to which should be used in which scenraios.
also what is the Setup Level Difference in both.
If you have any white paper / document / note in metalink also on this topic then I will be very happy to have that.
Thanks very much in advance.
Regards

Hi
Inter project billing may be used within the same operating unit.
Intercompany billing may be used only accross operating units.
Inter project billing means the provider organization is charging a separate provider project.
With intercompany billing provider organization is charging the same project as of the receiver organization.
With inter project billing the provider project may bill the receiver in any billing method as any contract project. With intercompany billing the billing is based on transfer price rules which may be only applied to actual expenditures of the provider organization.
There is full list of all setup steps in Oracle Projects Implementation user guide.
Dina

InterCompany Billing issue for the Free Goods?

Hi All,
I created the info record (MM) for the free goods determination in the STO with Condition Type NR00. When I am creating STO for the stock transfer from one company code to other, the free goods are determing automaticaly, but while doing the Intercompany billing system is considering the price for the free goods also.
Please suggest How to configure to determine the free goods while doing the Intercompany Billing ?
Regards,
C S Javali

Hi Javail
Any have all free goods so you can create the po indicator with free goods in receiving plant.
after delivery from supplying plant, you have to do the GRN in receiving plant.
so supplying pant value of goods zero ( P101 CONDITION TYPE). in this you have to specify if any other charges like transport etc. then do the billing.
Laxman

Free of Charge Intercompany Invoice process

Hello Experts,
I would like to know how the TANN, Free of Charge process works for intercompany Sales?
When I do the F2 billing document, the system behaves as it should but when I process the IV billing document, system is finding a price maintained at the PI02 level and adding that.
Your help will be mucj appreciated.
Saj

Free of Charge process in Intercompany scenario is not possible with standard configurations. Nevertheless, refer point no.4 in the following note:-
Note 33258 - Processing free-of-charge items
Also have a look at the following note:-
Note 33382 - Free-of-charge items in intercompany billing
Carry out the necessary modifications as recommended in the above notes and test.
G. Lakshmipathi

A Standard RRB report that shows actual project cost line items .... ?

A Standard RRB report that shows actual project cost line items but that also shows amount/qty by rejected, billed, to be billed, postponed?
I'm looking for something that will allow project managers to reconciile with the RRB totals and be able to dril in a see a level detail not available in RRB to decide what should be billed, what should should be deferred (postponed) and what should be rejected out of hand.
Thanks.

Thanks Virendra Pal but the VAx5 reports are not really the answer - maybe a custom report will be required right enough.

Default intercompany billing

Hi All,
Billing Type ZNIV (Copy of IV) should be the default billing type when I craate Inter Company Invoice (Purchase Order - Delivery - Inter Company Scenario).
In sales we can assign ZNIV document type to Order types so that ZNIV will be defaulted at the time od Inter comp invoice creation.
Same scenario If i create a Purchase Order and delivery, defaulted billing doc type is IV actually it should be ZNIV.
Where can I link ZNIV document type to PO or Delivery?

Hi,
To solve this issue you need to maintain two seetings
1.Maintain intercompany billing type in Sales order controls (VOV8) :- which you already have done
2.Maintain copy control in Delivery to Billing copy control in Tcode VTFL.
Here you can copy the exsisting standard copy control for LF to IV and change the billing type to your ZNIV billing type.
So whenever you will create the billing as per VOV8 and VTFL settings ZVIN will be defaulted.
Reward points if useful
Regards,
Amrish Purohit

Intercompany billing between 3 companies

Hi SD gurus
i am facing problem in configuring a unique scenario i.e. intercompany billing between three companies. I have to configure the below scenario in SAP :
Company code A gets an order from Customer, product delivery is from company code B to direct customer. As per standard SAP process Billing is from Company code A to customer and there is a intercompany billing between Company code A and Company code B. but in my case there is one other company code C involve in this process. due to this now intercompany happens between B to C and C to A. do we configure this in SAP standard scenarios ? if not can anybody suggest how can we do this ?
Deepak

Hi Terry,
We have done a very similar kind of scenario for our client. We have done it for 4 company codes. Actually, standard SAP can handle intercompany sales between only 2 compnay codes. So, this requirement (with 3 companies) calls for an enhancement. You will have to create a couple of Z tables to achive this scenario. First Z table to update the partner function and the second one for the selection of sequence in which the companies need to be billed. And you can use a BAPI (BAPI_SALESDOCU_CREATEFROMDATA) to create intercompany invoices from company B to C further automatically. Hope this gives you an idea to start the work. Let me know if you need any further help.
Regards,
Raghav

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

Intercompany billing document setup

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

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

Actual Batch COst to charge intercompany billing

Similar Messages

Maybe you are looking for