idoc（IDoc）.docVIP

idoc（IDoc） This is what I have seen some information, you can see, not very detailed: What about a IDOC, that is, a container for Business Object?. Each IDOC consists of Control, Record, Data, Records, Status, and Records. In Control Record, you can define Message Type to define the function of this IDOC. Data Records is the specific data. Physically linked to a list. Status Records shows the status of the IDOC operation. Suggest IDOC, ALE, two learn together. Take a look at the official website of SAP: Http:///saphelp_47x200/... 4f/frameset.htm There are a lot of systems in the world, just SAP itself, a lot, APO, R/3... Every system has many versions, 3.X, 4.X. Other companies also have many proprietary systems. Imagine a situation where my sales software uses SAPs SD, but my personnel management software uses HR developed by myself. We need to implement data sharing between these differentiated platforms for business purposes. For example, look at the performance of a salesperson and how much salary should be paid. The performance is in the SD, and the salary is in the HR. The middle share is about the basic data definition of the salesperson. Heres the question, how different platforms are like different countries, and how to make sure that their communications (Languages) are easy to understand IDOC is defined as a standard data transfer format, it can be said to be a world language. The most comprehensive document is SAPs Help music. But to be honest, SAP is far less MS than documentation, and it may take more time. Moonin, and one more question, what does the IDOC document refer to as ALE, ALE, and IDOC? What is the function of it? Through IDOC, you can pass various business data between the SAP systems (between R/3, R/3 and R/2) For example, when I send a material master data from the transmitter to the destination machine, the destination machine triggers the default program to generate such a material Of course, you can also modify the default processing mo