STO for Inter company with billing and delivery

Hi,
We have one compnay code e.g CXYZ with plant PXYZ now recently we have create new compnay code CABC with plant PABC assign to this new compnay code now as per our requirement we want to set up procedure for STO so both compnay code are supplying as well as are receiving plant in first case
PXYZ is supplying plant of comp CXYZ and
PABC is receing plant of comp CABC
now I have create a vendor in recieving and have assign the palnt PXYZ to that now I want to confrim in which compnay code the customer code to be create and in customizing Define Shipping Data for Plants for my receving plant PXYZ which customer code to be enter and also sales organization details to be enter of which company code CXYZ or PABC.
regards,
zafar

Hi,
PXYZ is supplying plant of comp CXYZ
point
1 assigen sales area of CXYZ to PXYZ
2) Material Mater with sales view
PABC is receing plant of comp CABC
1) create customer xdo1 with company code CABC and sales area of of CXYZ( which assigen to pant PXYZ)
2) assigen this customer number to to plant PABC
3) create vendor master in comapny CABC and assgine dupplying plant PXYZ in that vendor master record
document type nb
delivery type -nlcc
Regards
kailas

Similar Messages

Different sales area for Inter company stock transfer and STO

Hi People,
                       Is it possible to have two different sales area's for Inter company stock transfer and within the company stock transfer. The problem is in below step
IMG->MM->Purchase Order->Setup stock transport order->Define shipping data for plants.
In this step when you define plant as customer, the same plant as customer needs to be maintaind for both STO and Inter company and there is only one entry of sales area possible for this single plant. So, how can the task be achieved.
I want that STO should be carried out by sales area lets say X/Y/Z
Inter company should go through A/B/C.

hi dear,
           It is not possible at all to have two sales area for given Plant in STO.
           What is issue in that u can Transfer any MATERIAL, just need to extend it to given sales area.
Reagrds
AJIT K SINGH
HAPPY TO HELP U

MRP FOR INTER COMPANY- WITH 1 RECEIVING AND 3 SUPPLY PLANT

i have the following scenario:
1) i have company 'A' under company code 1000( purchasing plant) and it has 10 depos namely( A1 TO A10).
2) i have another company 'B' under company code 2000( manufacturing plant) .
3) under company code 'B' it has three manufacturing plant namely B1,B2 and B3.
4) Products x,y and Z are produced in all three plants namely B1,B2 and B3.
5) company 'A' receives the forecast for the year and give the requirement for all the three products(X,Y and Z)
to company 'B'
6) Based on the input from company 'A' icompany 'B' produce and sell all the final products(X,Y and Z) to
company 'A'.
7) company 'A ' and 'B' comes under same management and control area.
8) How to map into sap and how the requirement will be transferred from company' A' to 'B' and total stock
available under plants B1,B2 and B3 should be considered for MRP run for final products X,Y and Z.
( currently requirement is passed between executives of two company in the meeting).
9) some times the company 'B' has to deliver the final product to any of the depos( say A3 or A6) which is
situated near plant B1( under company code B) on instruction from company 'A', but the payment is paid only to company 'A' .This is done to avoid transit delay and transportation cost.
How to map into sap scenario
regards,
sekar chand

Hi Sekar,
MRP can be done only based on the Plant wise.
Please post it in PP and check
RR

Re : Organizational data for inter-company billing

Hi
While doing intercompany settings (img - enterprice structure - SD - assign sales org - disribution plant) i am getting the following error
" Organizational data for inter-company billing
missing in plant SUDA "
How to solve.
Thanks
Anto

Hi Anto,
IMG check wheather you assing Supplying company sales area to Supplying plant.
IMG->Saes&Dsitr -> Billing -> InterCompany Billing-> Assign Organizational unit by Plant
Select Plant (supplying company) and assign Sales org, Distbn Channel and Division of supplying company.
Regards,
M.Manickam

Organizational data for inter-company billing missing in plant 2200

Organizational data for inter-company billing missing in plant 2200

Dear Siva,
This may be related to incompleteness in the inter -company billing configuration settings so go through this IMG path then do the proper settings,
SPRO>Sales and distribution>Billing>Inter company billing>Assign organisational units by plant, here you need to assign the Sales organisation,Distributional channel and Division (sales area) to the 2200 plant.
Now you try
I hope it will help you
Regards,
Murali.

Using AR Invoice but for Inter-company but with Workflow Approvals

My client is using AR invoices (FV70) for inter-company transactions for other businesses that are not yet on ECC. They also utilize workflow for their normal manual journal entries which can go through up to 4 approval paths one of the latter which requires an inter-company approval. Does it make sense for inter-company transactions that will begin with the AR invoice to go through the same approval paths from the beginning similar to how they wish to do it for regular journal postings (FV50)?

If the location of the companies is the same then Approval Paths does not make sense, however depending upon location changes and more importantly if their are different indirect tax liabilities on the two participating companies then the system might be required.
Regards,
Akhileshwar K

Inter Company Sales & Billing

Dear All,
Could you please suggest while configure the inter company billing. I has search in our forums. Some what i understand but still i have some doubts on experts explanation. Could you please help me on Inter companysales & billing config & customization process step by step
Thanks in advance
Anjali

HI
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: XD0
The ordering sales organization is represented as Internal customer of Supplying company code.
We need to create customer master in Account Group u2013 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 codeu2019s 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 u2013 Pricing Procedure for Inter company billing is assigned to the combination of:
1) 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.
Regards
Amit Gupta

Billing and delivery address to be displayed in PO

Dear Gurus,
Here client requirement is as follows : There are three plants in three different places- Chennai, Bangalore and Hyderabad. Client is creating PO from Chennai plant and they want the material to be delivered in Bangalore plant. They want this to be displayed( billing and delivery address) in the purchase order. Kindly suggest me how to map this scenario.Thank you.

Hi,
For delivery adress you can use the subscreen for delivery adress in the item of the PO.
Por billing adress, if it's not the same that the adress for the center, you can do a subroutine for the form (Z)MEDRUCK for the company of these center, of you can create a partner 'Billing adress' and write it in form with a subroutine (Z)MEDRUCK.
I hope this helps you
Regards,
Eduardo

Reinitialize Sales Orders, Billing and Delivery (11, 12 & 13)

Hi,
Due to continues rollouts we need to reinitialize Sales Orders, Billing and Delivery do-cuments from R/3 into BW.
This requires us to delete all loaded data, logs, queues etc. on the BW side - Fair enough.
The real challenge come as we need to run the transactions OLI7BW(order), OLI8BW (billing), OLI9BW (deliveries) on the R3 side in order to fill the setup tables. Here we need to switch the "block all orders" on in order to ensure that no new documents are created while load-ing.
In relation to the above situation I have a couple of questions:
Is there no way of doing this in a more "online" fashion?
What transactions are actually blocked by flicking the "block all orders"?
Thanks in advance
Michael Bisfelt
Arla Foods a.m.b.a
Message was edited by: Michael Bisfelt

Hi Michael,
I've seen this process accomplished without blocking orders, but instead by blocking all transactions that may in any way lock an order or related sales document. Also, you can dramatically speed up the process of gathering the old documents by running multiple batch jobs (with different document number ranges) at the same time. In this case, I believe you want to "uncheck" the "New run" flag. I've seen runtimes for this reduced from over 24 hours to under 4 hours. The important thing is that you don't want to have ANY activity that modifies or locks order documents until after the date and time of termination that you specified, otherwise you will lose data on your transfer to BW.
Regards,
Chris

Tax code field under INVOICE Tab to be Mandatory for Inter Company PO

Dear All,
In MIRO Tax code field under INVOICE Tab to be Mandatory for Inter Company PO u2013 ZNB & ZRT for company code 0001.
How do we set as mandatory fields for those two intercompany document types.
Regards,
Teja

Hi
If u want to maintain tax code as mandatory field in PO?
Then SPRO- SAP IMG- MM- Purchasing - Purchase order- Define document types
In this check the filed selection key for the document types.
Then select the SPRO- SAP IMG- MM- Purchasing - Purchase order- Define svreen lay out at document level.
In this for the field selection key select GR/IR control and click on tax as required. and then save
It will not allow to create PO with out maintaoning tax code.
If u want to do tax code as mandatory in MIRO
Then Go to OLMRLIST and make changes accordingly.
Thanks
Raman

Asking to maintain a valid document type for inter company

Hi friends
We have created a purchase order. It is STO inter-Co
There is no issue for a normal vendor when posting in MIGO; the error is just for inter-company vendors.
When doing MIGO the document shows OK. When posting or saving the document it is showing an error as Use a valid document type for inter company.
As per the error we have maintained the document types in OBA7 and the inter company posting are checked for the document types.
Can anyone help me on this issue how to proceed?

hI SUKANYA
PLS EXPLAIN ME WHILE GL A/C CREATION FOR WE ASSIGNED G067 AND READY FOR A/C INPUT IS FOR WHAT
CAN U PLS EXPLAIN ITS USES . MEE ANSWER KOSAM WAIT CHESTUNTAA
THANKS
MALLIKARJUNA

Calling billing and delivery transactions when i click the button in webdyn

Hi,
How to call the transactions like billing and delivery when i click the button.I am developing a webdynpro alv report in that 2 buttons are there.one is confirmation and another is cancel.
I want to call the billing transaction when i press the confirmation button?

Hi Lakshmi,
It is not possible to directly call a transaction code from a wev application. Calling a transaction involves launching of SAP Dynpros which is not supported by WDA frame work.
One possible ways is to use transactional iViews in Portal. We can Associate a transaction code to this and when called, it launches the same in an R/3 Screen.
If you are using portal as a triggerring point of your web dynpro applications, then the below requirement is achieved by doing the following.
1. Create a BDC report program to call transaction CAT2 skipping the first screen.
2. The report has the same input parameters as that of the transaction CAT2.
3. Associate a transaction to the report program sat 'ZCAT2'.
In the event handler of the button in your web dynpro do that following
Data declarations
Local Internal tables(lt_)
lt_bus_parameter_list TYPE wdy_key_value_table,
lt_launcher_parameter_list TYPE wdy_key_value_table,
Local Work area's(ls_)
ls_keyvalue_pair TYPE wdy_key_value,
Local Variables(l_)
l_pcdpageurl TYPE string,
l_componentcontroller TYPE REF TO if_wd_component,
l_port_manager TYPE REF TO if_wd_portal_integration.
Constants(c_)
CONSTANTS:
c_transaction_code TYPE string VALUE 'ZCAT2',
c_okcode TYPE string VALUE 'F8',
c_param1 TYPE string VALUE 'P_Data_Entry_Profile',
c_param2 TYPE string VALUE 'P_person_number'.
l_componentcontroller = wd_this->wd_get_api( ).
l_port_manager = l_componentcontroller->get_portal_manager( ).
Fill all the business parameters
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = c_param1.
ls_keyvalue_pair-value = 'Data Entry Profile'.
APPEND ls_keyvalue_pair TO lt_bus_parameter_list .
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = c_param2.
ls_keyvalue_pair-value = 'Person Number'.
APPEND ls_keyvalue_pair TO lt_bus_parameter_list .
Fill the launcher parameters for the transaction
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'AutoStart'.
ls_keyvalue_pair-value = 'Yes'.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'GuiType'.
ls_keyvalue_pair-value = 'WinGui'.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'OkCode'.
ls_keyvalue_pair-value = c_okcode.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'System'.
ls_keyvalue_pair-value = 'SAP_R3_HumanResources'.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'TCode'.
ls_keyvalue_pair-value = c_transaction_code.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'Technique'.
ls_keyvalue_pair-value = 'SSF'.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
CLEAR ls_keyvalue_pair.
ls_keyvalue_pair-key = 'WinGui_Type'.
ls_keyvalue_pair-value = 'Shortcut'.
APPEND ls_keyvalue_pair TO lt_launcher_parameter_list.
SAP has provided us with customizing table to maintain the path for the iView.Here Resource_key is the key field to get the path.
We create a new entry in this table using which we uniquely identify the path of the iVew that needs to be launched.
get the url of the pcd page for the common transaction iView
SELECT SINGLE b~text
INTO l_pcdpageurl
FROM t7xssserstring AS b
INNER JOIN t7xssserres AS a
ON a~respcdpage = b~guid
WHERE a~ressource = /rio/zcl_hse_constants=>c_common_resource.
Navigate to the Injury Illness details
CALL METHOD l_port_manager->navigate_absolute
EXPORTING
navigation_target = l_pcdpageurl
navigation_mode = l_port_manager->co_show_external
use_sap_launcher = abap_true
business_parameters = lt_bus_parameter_list
launcher_parameters = lt_launcher_parameter_list.
The folowing is the flow of the program:
When user clicks a button to launch transaction CAT2, the event handler associated to it called.
Here we populate an internal table with the parameters to call transaction ZCAT2 and the iView is launched by calling navigate_absolute method with the right path.
I am not very much sure as to how the iViews are set up but there is a provision to read the key valure pair there. The values are read and the tranzation ZCAT2 is called which will inturn launch CAT2 transaction.
By adding Skip First screen statement we can get in the details directly.
Hope this helps.
Regards,
Sravan Varagani

Asking to use a valid document type for inter company

Hi friends
We have created a purchase order. It is STO inter-Co
There is no issue for a normal vendor when posting; the error is just for inter-company vendors.
When doing MIGO the document shows OK. When posting or saving the document it is showing an error as Use a valid document type for inter company.
Can anyone help me on this issue?

Hi
This problem raised If the trading partner assigned in the Vendor master in Control data and that trading partner is different fromt the trading partner assigned to particualr Co code.
Goto TCODE:OBA7 , selec the document type for which this error is coming - in the document type screen in control postings sections select the inter-company postings check box.
VVR

Return procedure in STO plant to plant with billing(single co code)

Hi,
I'm doing STO plant to plant with billing in one company code.
But I have one query. Suppose I'm in plant B(Receiving).
From plant A(Supplying), I have received material.
I've done goods receipt
But after that I found few material defective & now I need to return it to the supplying plant(A).
I have already capture & post excise invoice.
I want to reverse the same.
Please help me.
Thanks & Regards,
Piyush

Hi Pyush
Try cancelling the GR,then post the PART 2 again,now system wil reverse the accounting entries,then cancel the excise invoice.
Try in your quality system and confirm
Regards
Ratha

Excise Duty handling for Inter company Stock Transport Orders in SAP 4.6C

I want to handle Excise Duty handling for Inter company Stock Transport Orders in SAP 4.6C. I know that SAP has provided standard solutions in 4.7C by giving one standard table OIH09 which can be maintained through Customisation.
In 4.6C, even the Goods issue & Goods receipt button in item details of Stock Transport order is not available.
Is there any work around for the same.

In IS-OIL, cross company postings were stopped with Note # 623910 & would
require a core modification to achieve this functionality.

STO for Inter company with billing and delivery

Similar Messages

Maybe you are looking for