PI01 Intercompany Billing*
Dear SAPpers,
what does that mean by raising sales order in Intercompany and u become the error "Requirements are not ulfilled for conditions PI01" althought all the steps have been respected? Please help me by giving me steps.
Thanks
Hi,
When the Plant of the sales order line item is assigned to different company code with sales organization's company code the sales order is called as intercompany sales order.
In Pricing procedure V/08, condition type PI01 is assigned with requirement 22 - Inter-company will be assigned. it ensures that the document is an inter-company billing document. Inter-company billing documents are created for inter-company sales transactions and represent the delivering company code's bill to the sales organization's company code.
Regards,
Muthu
Similar Messages
-
Intercompany billing - using condition type PI01 = VPRS
In the intercompany billing we are going to configure the condition type PI01 to copy the amount in the condition type VPRS in the order. Can anyone give me a proposal of how to do this?
Hi,
Check copy controls from Delivery to blling document - VTFL is there any thing missing Header as well as item level, at what lelvel your determining the price. pricing at main item level or batch level.
Pricing should be at main item level
There will be two items 1 is main item 2. is Batch item
chek cumulate cost has checked on main item or not
and also gothrough the related Notes:
Regards,
MH -
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 -
Created a consignment fillup order/ delivery /transferorder
Unable to create a intercompany billing document IV ... when i see the log in VF01 it says "Sales organization is not defined".
Can anyone help me with this please???hi
Customer orders goods to company code/Sales organization A (Eg.4211/4211).Sales org 4211 will accept and punch the order in the system with sold to party as end customer code in the system. Company code/sales org B (Eg.4436) will deliver the goods to end customer and raise an intercom any billing on 4211 with reference to delivery. This can happen only after 4211 raises invoice to his end customer to whom the material has been delivered by 4436.
SPRO Customization required:-
1. Assign plant of delivering company code (Eg.SI81) to sales org/distribution channel combination of ordering company code (Eg.4211/RT)
2. Maintain intercom any billing type as IV for sales document type OR
3. Assign Organizational Units By Plant (Eg.SI81/4211/RT/11)
4.Define Internal Customer Number By Sales Organization (Eg.4436 will create customer master for 4211 company code and that number will be maintained in this relationship:-4211/231)
5. Automatic posting to vendor account (Optional)
6. Maintain pricing procedure determination for 4211/RT/A/1/RVAA01-For customer sales and billing
Maintain pricing procedure determination for 4436/RT/A/1/ICAA01-For intercompony billing
Master data to be maintained:-
1. Create end customer master in company code/sales org 4211/RT/11
2. Create customer master for 4211 company code/sales org in 4436/RT/11
3. Maintain PR00 as price for end customer-Active in RVAA01
4. Maintain PI01 as price which has to be paid to 4436-Statistical in RVAA01
5. Maintain IV01 as inter-company Price-Active in ICAA01 -
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
STO Intercompany Billing
What is the appropriate at Pricing procedure to maintain to the IC STO Billing document.
RVAA01 or ICAA01 both to be maintained ?
Reg
R.G.Hi,
The mentioned Pricing procedure are Standard procedures and In order to Process intercompany billing we have to use a Condition type a IV01 ( new ) or PI01 Old and this has to be assigned to pricing Procedure Field in master data in Condition type IV01.
In standard Intercompnay Billing is ICAA01.
Regards
Shekar. -
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...
BawaDear 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 -
Hi Gurus
Please help me in getting the steps for the configuration of the Intercopany billing process in SD
RajuHi Raju
Following is the step by step procedure to create intercompany billing
Step: 1
DEFINE ORDER TYPES FOR INTERCOMPANY BILLING
Path: IMG -- SD-Billing -- Intercompany Billing -- Define Order Types for Intercompany Billing.
Step: 2
ASSIGN ORGANISATIONAL UNIT BY PLANT
Path: IMG SD --Billing -- Intercompany Billing -- Assign Organizational unit by Plant
Here Assign sales org-dist channel-division to Del1 which is sister concern co. plant
Step: 3
EXTEND CUSTOMER
Extend a customer of us05 sales organization i.e. eg.7000006001 to dell sales org. in customer master data. This is the customer who is actually ordering for the material.
Step: 4
ASSIGNMENT OF SALES ORG - DISTRIBUTION CHANNEL -PLANT
Path: IMG -- Enterprise Structure Assignment -- SD
Step: 5
Create Customer and assign customer number to Dell Sales Org ie e.g. 100358 (payer) This customer is nothing but the corporate office. We assign a customer no. to the corporate office. This corporate office will be assigned as an internal customer.
T-code: Xd01
Step: 6
DEFINE INTERNAL CUSTOMER NUMBER BY SALES ORG
Path: Img SD --Billing-intercompany billing -- Define internal customer number by sales org
Step: 6
MAINTAIN CONDITION RECORD T .C
T-code: VK11 -- PI01
Here we maintain the price for intercompany that is for the corporate office.
Step: 6A
T-code: VK11PR00
Maintain a condition record for material sales org-US05 and dc- U4.
This PR00 is for the customer who is actually ordering the Material.
Step: 7
Create Sales Order
T-code: VA01
Then create Delivery and Billing
Reward if useful to u -
Free goods in intercompany billing
Hi,
I customize free goods functionality in SAP and all seems to be all right. A sales order makes a delivery with the two itens and after that the invoice have two itens one of then with condition TANN. Everything is perfect...
But may question is: how can i do this in intercompany billing once in this kind of billing i haven´t the sales order but a purchase order?
Best Regards
João FernandesFree goods cannot be used in make-to-order production, third-party order processing and scheduling agreements.
This is the Limitation of setting up free goods
Cheers -
List the intercompany billing numbers from sale order numbers.
suppose i have a set of sale order numbers. is there any report can list the intercompany billing numbers related to those sale order numbers? i don't want to use VA03 because it can display only one sale order number.
thank you very much,
AnekHi Anek,
Run the transaction code VA05. Click on the Further Selection Criteria, Select the check box 'Sales Document Type' and click OK. System will ask for the Sale Document Type. ENter the inter company Document Type, Press Enter and select the date range press Enter.
System will list the orders.
Hope it helps. Let me know whether it resolves you issue.
Thanks & Regards,
Nagaraj Kalbavi -
Automate creation of Intercompany billing document
Hello All,
We have a requirement to automate the intercompany billing document to be created whenever F2 billing document is created ( without using VF04).
Any input regarding this will be greatly appreciated.
Thanks,
NagarajuAfter 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. -
Pricing in InterCompany Billing document for InterCompany Stock Transfer
Hi, SAP Gurus
I am doing Stock Transfer Order using Intercompany Billing. When I am creating the Intercompany invoice I am not getting the pricing in the conditions tab. There ar eno condition types. I have maintained the pricing procedure determination in OVKK. Still there is no pricing procedure determined.
Please suggest.
Thanks
JayantDear Jayant,
Just check document pricing procedure and customer pricing procedure
whether it is maintained properly or not.
warm regards,
Rahu; -
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,
AnubhavHi,
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,
BalaHi,
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 -
Different currecny in intercompany billing
Hi Friends ,
My process flow is Purchase order - delivery - intercompany billing . In the PO currency is Newzeland dollor . Where as in the intercompany billing, it is picking up doc currency as USD, obviously from sold to party . I need to bill this in NZD only without changing the existing currency ( USD) in the sold to pary master record.
I tried with different options in ' Price Source' field in copy controls but it doesn't work .
How can I do that ?
Regards
Mahesh.In this case the sold to party is a Plant , and billing would be majorly in USD . This is first time we need to bill in other currency and going forward we may have to use different currenies ( other than USD and NZD ) on quiet a few occassions . So we cannot afford disturb the sold to party master record .
What are the ways to about it ?
Regards
Venu
Maybe you are looking for
-
Hi All I am creating SD billing for factory sale (pricing procedure JINFAC), which is involved excise duty as well. VF01 is creating two doc , one for Billing document and one for Excise JV (as we opted Excise invoice during billing). The issue is i
-
How to read a web page as an ascii file
I need to open an url and read the contents, as it were a simple local ascii file. This give me just garbage, as [B@fd2e84b (that change every time, seems to be a memory address, not the contents..). <pre> import java.io.*; import java.net.*; try { U
-
please help.....walk through
-
Hi all, Can anyone tell the table and field for date of manufature in production order confirmation screen.... Regards, Joseph
-
I cannot find all my drivers in this site. I have HP Pavilion 15-n215sx Notebook Product Number: G7E77EA OS Windows 7 Ultimate 64 Bit This is a link for my product drivers on hp site http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=