EDI between intercompany

Hi,
We are going to have EDI functionality between intercompanis, where cost will be rolled up through WBS at the order level. Just wondering if EDI funnctionality offers any three/two way match. If yes, then how!
Any suggestion will be most appreciated.
Thanks
Ashok

Hi,
You can work with Inbound delivery created via IDOC Triggered from Outbound Delivery. Please refer this wonderful note, which will explain you a lot of things, Note 1119073 - FAQ: Automatic inbound delivery creation for stock transfers
Regards
Chandra Shekhar

Similar Messages

Difference between intercompany sales and STO (inter)?

HI Experts
Can any one tell me what is the difference between between intercompany sales and STO(inter)?
LNaidu

hi..
Intercompany sales trans.
the customer orders stock from the sales org (3001)..that belongs to comp code 3000...the Sales org 3001 then creates the sales order and indicates the delivering plant as a plant that belongs to different company code i.e. 1000..
The sales org 3001 then invoices the customer for material purchased..the system automatically creates the inter-compnay billing doc at the same time as the customer's billing doc is created,,,This inter-compnay invoic ius sent from the delivering plant to selling sales org..
Two billing doc..1. standard customer billing doc that is sent from the sales org to the customer.
2. inter-compnay doc that is sent from delivering plant ot sales org..
Inter compnay STO..
comp code 3000 has plant 3000 creates purchase order to purchse stock from plant 1000 based in comp code 1000..
the stock is delivered to plant 3000. comp code 1000 then creates an inter compnay invoice and bills compnay code 3000 for the stock...
hope it works..
Thanks

Relationship between intercompany PO/delivery

Hi Experts,
Is there a report or any other method that can display the relationship between intercompany PO and delivery? Our customer does not want to check PO history in ME23N one by one, and they do not have authorization for SE11/16. is there any other method?
Thanks,

Hi Chinna,
I failed to see the delivery number in ME2W/MB5T, but only the PO number. Can you please tell me how to check the delivery number?
Regards, Helen

Difference between Intercompany sales,thirdparty sales

where th eexact difference comes in configuration in third party sales,intercompany sales .explain with examples
regards,
cpdatt

Hi,
Go through the explanation given below with test cases.
Business case: -
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
Process:-
1. Create OR with sold to party as end customer.
2. Plant to be selected is delivering plant belonging to different company code. With this selection system will treat this order as intercomany sales.
3. Pricing procedure is RVAA01
4. With reference to this order delivery will be created from the delivering plant and post the goods issue for this delivery.
5. Ordering sales org will create billing document F2 with reference to delivery for end customer.
6. Delivering sales org will create intercompany billing IV with reference to delivery document.
I hope this helps you.Reward points if solution is useful.
Regards,
Amrish Purohit

Posting via EDI for Intercompany billing

Hi all,
I have a situation where when I create an IC posting the System creates a subsequent posting in the Other company code.
My problem statrs in SD
We have a condition where we have a surcharge fee for a particualr oder
This surcharge fee should go to an additional Ac and not cost COGS.
In the SD doc we have a condition set up in header
1.IV01     Inter-company Price     blank
2.YHF1     Handling fee IC     10.00
Position level
IV01     Inter-company Price     109.36
YHF1     Handling fee IC     10.00
this is because the 10 $ should be charged per oder not a per position.
in seeting up the EDi everything is set up but when creating the Ic IDoc it come up with an error
in the Transacion i have set up the fields like this
Indicatiors for Transfer
Calculate Tax
Header Surcharg and items surcharge
BDc sess
the posting details are standard
when I Assign G/L Accounts for EDI Procedures
partner Type LI
+IV01     All COGS           account no 3000000
+YHF1     Handling Fee IC   account no 3111000
but somhowe it wont post anthing to the 3111000 ac no matter what combination i use in the parameters

Hi Dave,
Could you possibly forward me your solution please, I have a similiar problem.
Much appreciated,
Kind regards,
A.D. Botha
[email protected]

Difference between intercompany and intra company transactions

Hello,
I would like to understand the SAP functional concepts and implications and difference as well of the inter company and intra company elements in sap as well as in a business perspective. If anyone can help me on this please that would be really appreciated. Thank you
Kevin

Hi
Check this link for Inter company STO
http://www.sap-img.com/sap-sd/configure-intercompany-stock-transport-order.htm
For intra company STO
http://www.sap123.com/showthread.php?t=176
Regards,
Raman
Edited by: Raman S on Apr 1, 2009 2:37 PM

Subcontracting between intercompany plants

Dear Experts,
Can anybody tells me the configuration required for subcontracting between plants belogs to different company.
Suppose A Plant sents material for job work to B Plant which, belongs to different company. We have created a vendor code for plant B and send the material thru subcontracting cycle. Now problem coming with Plant B. How Plant B prepares the invoice and stock reduces from Plant B.
Needs Config setting. Full Points will be given for helping answers.
Thanks
GR

Friend
Two solution can be thought of as two solutions
solution 1
Sucontracting company does not want to track inventory and caputre subcontracting costs incured then follow the following
Maintian vendor master linking to customer master ( subcontrancting comapny vendor and customer)
Vendor for expensing subcontracting charges, customer master if you want to follow SD delivery
Detail configuration is as mentioned below
1. SPRO -Materials Management -Purchasing -Purchase Order - Set up Subcontract Order
In the grid enter Supply plant code from where Input materials to subcontractor have to be delivered) and the Delivery type "LB" which is SAP Standard Subcontract delivery type
2. Shipping point definition
Spro - Enterprise structure - Definition - Logistics executin - Define copy,delete, check shipping point
3. You should have set the shipping point for that plant which is done in
Spro -Enterprise structure - Assignment - logistics execution - Assign shipping point to plant
Check the following setting are also done
4. Shipping point determination
SPRO-Logistics Execution - Shipping -Basic shipping functions -Shipping points and Goods receiving points determination - Assign shipping points
5. Delivery type definition
SPRO - Logistics Execution -Shipping- Deliveries - Define Delivery types
Last but not the least
6. Material master should have sales1, sales2 and sales/plant view extened with necessary data like loading group, transportation group etc
7. Customer master should have been set for respective company code and sales organisation
Solution 2
Create Cross company STO. Create Production order in the Subcontracting company (its plant) and capture material consumption and caputre overhead costs. Create additional STO to send finished material back.
ENJOY SAP
Regards
Edited by: Gopal SP on Apr 2, 2008 12:39 PM

Difference between US eliminations and "normal" intercompany eliminations?

Hi,
Can a kind soul please explain the differences between intercompany eliminations and US eliminations please?
Thanks

Hi Varda ,
RDA is Real Time Data Acquisition . In this We can retrieve Live data . While using Normal DTP We can t pull live data
For example :- Today We have Create a 50 orders . This 50 order information pulled after completion of sales order creation . we can t see live . But RDA process pulled the data at the point of sales order creation it self ,It support only Stranded DSO .It will use Some industries like FMCG.Retail,banking sector they want to know current data information from BI Side then RDA.
Please Find below link for Demonstration of Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00db64ee-82f0-2b10-01b0-fe9543dc227e?quicklink=index&overridelayout=true.
Real-Time Data Acquisition (RDA) for SAP BI 7.0 using Web Services API
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20f704bd-b6e8-2c10-569e-d726784388ce?quicklink=index&overridelayout=true
Thanks & Regards,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://www.bluemarlinsys.com/
http://bluemarlinsys.com/bi

Difference between ALE / EDI

Hi,
I have a question from long time. What is the difference between ALE & EDI.When I ask my friends They say in simple way. SAP - SAP (ALE) . SAP - NON SAP (EDI).
Today I read in a book .ALE/IDOC method can be used to connect to SAP - NON SAP (LEGACY). Now I am more confussed .
If any one can explain me the real difference I really appreciate the time.
Thanks,
Andy

Hi Andy,
I am just sharing a few lines which i read some where. Hope that would be helpful.
ALE(Application Link Enabling) refers to the losely coupled systems whereas the EDI speaks about the Electronic Document Exchange. We need to enable ALE in order to use the EDI feature. ALE builds the bridge and EDI is the means by which the data moves in and out of the SAP system just like vehicles moving over the bridge. IDOC(Intermediate Documents) are the data containers which will be moving in and out of SAP carrying data.
Thus summarising we need to establish ALE between the systems in order to use EDI between them. In case we need to use EDI between SAP and some other target system then we need a EDI subsystem which understands these IDOCs and converts into the format understood by the target system.
Hope this is useful.
Regards,
Pooja

Main Difference Between EDI and IDOC Based On RFC

In IDOC ,RFC is Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
What About EDI ?

Hi Saurabh,
Check this..Hope it helps you.
EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents (IDOCS).
EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.
EDI is also called paperless exchange.
Advantages:
Reduced Data entry errors
Reduced processing time
Availabilty of data in electonic form
Reduced paperwork
Reduced Cost
Reduced inventories and better planning
Standard means of communications
Better business process
EDI has two process
1. Outbound process
2. Inbound process
OP:
1.Application document is created.
2.IDOC is generated
3.IDoc is transferred from SAP to Operating system layer
4.Idoc is converted into EDI standards
5.Edi document is transmitted to the business partner
6.The Edi Subsystem report status to SAP
IP:
1.EDI transmission received
2.EDI document is converted into an IDOC
3.IDOC is transferred to the SAP layer
4.The application document is created
5.The application document can be viewed.
IDOC:
IDOC is a container that can be used to exchange data between any two process.
Each iDoc is assigned a unique number for tracking and future reference.
iDoc Consist of several segments,and segments contain several fields.
iDoc contains the following three type of records...
1.One Control Record.
2.One or many Data Record
3.One or many Status record.
PORT:
Port is used in the outbound process to determine the name of the EDI subsystem program,the directory path where the idoc file will be created at the operating system level,the idoc file names and the rfc desinations.
RFC Destination:
Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.
Partner Profile:
Partner profile specified the various componets used in an outbound process ( Partner number,IDoc type,message type,Port,Process code),the mode in which it communicates with the subsystem(batch or immediate) and the person to be notified in case of errors.
Message Control
Used in pricing,account determination,material determination,and output determination.The message control component enables you to encapsulate business rules with out having to write abap programs.
Process:
Setup RFC destinations SM59
Port Destinations WE21
Partner Profile WE20
Message control NACE
Purchase Order ME21
Check IDOCs WE02,WE05
Explain to me about Idoc?
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.
Re,Manas

FAQL EDI vs ALE

EDI (Electronic Data Interchange)
      exchange of business documents (e.g. purchase/sales orders, invoices) between business partners (e.g. customer,
      vendor) by means of electronic messages
ALE (Application Link Enabling)
     integrated business processes across distributed systems with one company (e.g. replication of master data between
     several R/3 systems)
     distribution of master data, transactional data, and control data (i.e. application customizing)
IDoc (Intermediate Document):
     format in which SAP systems store application documents for transfer
EDI subsystem/converter
     external system that maps the IDoc format to international standards (e.g. UN/EDIFACT, ANSI X.12)

Hi Anandha,
     Differences :
          ALE(Application Link Enabling) refers to the losely coupled systems whereas the EDI speaks about the Electronic Document Exchange. We need to enable ALE in order to use the EDI feature. ALE builds the bridge and EDI is the means by which the data moves in and out of the SAP system just like vehicles moving over the bridge. IDOC(Intermediate Documents) are the data containers which will be moving in and out of SAP carrying data.
Thus summarising we need to establish ALE between the systems in order to use EDI between them. In case we need to use EDI between SAP and someother target system then we need a EDI subsystem which understands these IDOCs and converts into the format understood by the target system.
EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
      The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Intercompany transfer price

Hi All,
How to configure EDI for intercompany transfer price.
Regards
Nidhi

Dear Azeez
In Inter Company stock transfer scenario, it requires a transfer price which can be either PI01 which is a fixed price or PI02 which is percentage based.
Please go through this document and configure the process.
[Cross Company Sales|http://help.sap.com/bp_chemv1500/Chem_US/Documentation/Q84_BPP_EN_US.doc]
thanks
G. Lakshmipathi

Intercompany sales and intra company sales

Hi gurus,
please tell me what is intercompany sales and what is intra company sales?
and what is the difference between intercompany sales and intra company sales?

Hi,
please go through below links
http://help.sap.com/saphelp_470/helpdata/en/dd/5614e7545a11d1a7020000e829fd11/frameset.htm
Kapil

Intercompany sales vs intercompany stock transfer

Hi,
Wat is the main differences between
Intercompany sales vs intercompany stock transfer.
More over what are the taxes applicable (India) in both.
In what case VAT/CST will be aplicable and in what case it will not be applicable?
Regards
G A

Hi
Imagine this scenario
There are 2 company codes,2 sales orgs and 2 plants entire 2 set ups one in UK and another in INDIA
Company code UK and INDIA
Sales orgs UK and INDIA
Plants UK and INDIA
Now For a customer in INDIA and the sales order is registered in Sales org INDIA if the the goods are shipped directly to this customer in INDIA from plant UK which is assigened to company code UK then it is intercomapany sales
Intercompany sales means plant will directly sell or supply to end customer
Now after registering or taking this order from the customer in INDIA and if you transfer the stocks from UK plant to INDIA plant then it is intercompant Stock transfer and after getting the stocks this INDIA plant will supply the end Customer
intercompany stock transfer means the stocks are being shifted across 2 plants of different company codes
The main difference is the same as what is the difference between sales and stock transfer
Sales will happen to the end customer and stock transfer will happen between plants
In Intercomany sales the sales is happening to the end customer directly who is assigned to a different company code
In Intercomany stock transfer stock is moving between 2 plants of different company codes
Regards
Raja

EDI between intercompany

Similar Messages

Maybe you are looking for